You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On docker daily builds are delivered, when using for example:
Get-BCArtifactUrl –country nl –type Sandbox -version "25" -select all
I get a list of all delivered versions for BC25.
However if I take a specific build all apps are stamped with this version (25.2.27733.28209)
If I check an online sandbox, I can figure out that only Base Application and Foundation app were actually deployed to FAME.
Is there any for us to get the official delivered versions of apps into the online platform?
In the embed app scenario I have issues when delivering the tenant DB by using the latests artifact. For example if I would have used artifact: https://bcinsider-fvh2ekdjecfjd6gk.b02.azurefd.net/sandbox/25.2.27733.28209/nl
A problem will occur wirh apps:
Application and System Application as they are still using version: 25.2.27733.28023
Hope my question is clear?
The text was updated successfully, but these errors were encountered:
On docker daily builds are delivered, when using for example:
Get-BCArtifactUrl –country nl –type Sandbox -version "25" -select all
I get a list of all delivered versions for BC25.
However if I take a specific build all apps are stamped with this version (25.2.27733.28209)
If I check an online sandbox, I can figure out that only Base Application and Foundation app were actually deployed to FAME.
Is there any for us to get the official delivered versions of apps into the online platform?
In the embed app scenario I have issues when delivering the tenant DB by using the latests artifact. For example if I would have used artifact:
https://bcinsider-fvh2ekdjecfjd6gk.b02.azurefd.net/sandbox/25.2.27733.28209/nl
A problem will occur wirh apps:
Application and System Application as they are still using version: 25.2.27733.28023
Hope my question is clear?
The text was updated successfully, but these errors were encountered: