Closed CarloAxians closed 8 months ago
It looks like you are using the wrong approach. But just to verify: your want to publish your new version of the app to an online sandbox to test your AppSource app in that sandbox?
If so, the only way to do that is to use dev-port deployment.
You can do that with the "ALOps Extension API" step, and set up a "dev_endpoint" (like: "https://api.businesscentral.dynamics.com/v2.0/YourEnvironmentName/")
No, I want to update an app that is in the AppSource with the AdminCenter update API. https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/administration-center-api_app_management#update-an-app
So we have released a new version of our app in the AppSource and from DevOps we want to initiate the update process, in stead of manually perform the update from the Admin Center:
Ah - clear - will look into it!
Just meant as an update: we made significant progress on this. We decided to not do it as BCCH, but build smart features (auto-discovery) to make the deployment process easy. More soon!
More soon!
@waldo1001 I guess we've arrived at 'soon' in the meanwhile :)
Any news to share?
Well - in our next release, there will be a new step, which is going to be a very automatic approach to the upload.
Based on the apps that you download (artifacts), and the connection to your marketplace, it will figure out all offerings, search apps and library apps (dependencies) in the artifact folders, and update it online.
It's going to be a fully automated process, all you need to have is an offering online, and that app (and its dependencies) in some kind of folder on the build server.
Hi, I am facing the same issue when using ALOpsAdminCenterAPI to update an app. Is this still an issue in ALOps or am I doing something wrong?
Are you sue this is part of this issue?
This issue is about the AppSource upload - a step that has been released quite some time ago.
You are talking admincenter - which is not the same.
Hi Erik, If I read below, Carlo wants to use the ALOpsAdminCenterAPI command to update an already installed app on a BC cloud environment. That's exactly what I want to do. And I also get the same error.
My bad, sorry .. I was confused with another issue :-/.
ALOps should work - we are using it every single day to update apps.
Can you please send Yaml and Log?
No problem. I attached both now. I replaced tenant & client ID.
Hi, Were you able to find a cause/solution for the issue? We would like to start using app updates via ALOPs/DevOps. Thx
You won't believe it, but we were just setting up test-scenarios for this .. . And we believe we have a repro .. (as said, we're using this ourselve every.single.day - so we were surprised.. .
I'll keep you posted..
We performed a bugfix in the latest release - can you confirm it works now?
I just tried. Unfortunately, it's telling me that there are no apps available for update. But BC admin shows me there is a new version to install... Can you check please? Log.txt
Hi - Any news on this one please? We want to start using ALOps for App Updates soon. Thx.
Hm. We're gong to change the output so we'll print all available updates so we can figure out why this is not working ..
Good morning, do you have news on this one please?
Hello, any news please?
We have been trying and retrying .. but finally our eye caught a very stupid mistake .. . In stead of appId, we used Id .. so it was never using the right Id.
So sorry .. sometimes the simplest issues are the hardest to find :'(.
hotfix coming up
Hi, maybe I was a bit to early, but I just retried and it still doesn't work. Can you check please?
Describe the bug We want to update our AppSource app with the AdminCenter API.
the used yaml If we specify the app-id we want to update, we receive the error ##[error]*** 'App ID' specified, filtering updates
the output
the used yaml If we remove the app-id, we receive the error ##[error]Exception in BCConnector.PostAPIData: De externe server heeft een fout geretourneerd: (404) Niet gevonden.
the output
Expected behavior There are two API call's, the availableUpdates API should be without the app-id and the update API with the app-id. ../apps//update should be ../apps/app-id/update