Scope and SyncMode on AL-Go Settings won't work. #1137
Labels
documentation
Improvements or additions to documentation
enhancement
New feature or request
Fix Ready
Fix Ready
In Preview
Currently available in AL-Go for GitHub preview
Comments
|
If you include the log of the deployment step, then we might be able to see what is going on? |
|
Sure! Here it is: Hope it will help. |
|
Here is the one that failed: |
|
The deployment scope is only added to preview at this time - https://github.com/microsoft/AL-Go/blob/main/RELEASENOTES.md This above v5.2 is not included in v5.2 - and v5.3 will ship in 2-3 weeks. if you run Update AL-Go System Files with microsoft/AL-Go-PTE@preview - it should work. |
|
Hello @freddydk, First of all, thanks for your help. I've already done what you suggest, and it is still deploying it in Dev Mode and in SchemaUpdateMode=synchronize. Of course, I'm using the latest AL Go Preview. Here I attach you again the logcat, and hope we can find together a solution for this.
|
|
It looks like it doesn't find your settings at all. |
|
It's MXSandboxTest, but it doesn't have sense the way it tries to find the environment, as I think it has to find the name of the environment after the "-".
|
|
Then the deployto setting needs to be DeploToMXSandboxTest without the my- |
|
Okay, now it seems to be working fine @freddydk . This was an easy one I think. Just as a suggestion, to prevent anyone from fighting against AL Go with this scenario, it would be great if you can improve the documentation for 3 facts, I think it will help for a lot of people out there. 1- Scope and syncmode is only available at the moment for Preview. This issue can be closed. Thanks again for your help. |
|
Currently, the way to determine what's in preview and what's in a specific version is to look in the releasenotes and see under which version a feature is described. If it isn't under a specific version, it is either not yet released or in preview. I will add a small description to https://aka.ms/algosettings#deployto, explaining that the environment name to use for the property is the GitHub environment name, but in your case, the GitHub environment name and the BC environment name is identical, so I would like to know where you got On the setting not found - most environments won't need settings. It might however be a good idea to have the troubleshooting workflow look through settings for things like this - I will consider adding that. |
freddydk
added
documentation
|
I have added the troubleshooting item to the backlog: https://github.com/orgs/microsoft/projects/521/views/1?pane=issue&itemId=71625987 |
freddydk
added a commit
that referenced
this issue
Jul 23, 2024
freddydk
added
Fix Ready
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
After the setup of AL-Go, the pipeline always deploys in Dev Scope, and if a field or table is removed, then it won't ForceSync, always does "Add" mode. I've encountered this issue that is translated that after a minor update, all the apps published by the pipeline are removed, so the users won't find the customizations. I'm using the latest AL-Go System files, and I've executed the Update AL-Go System Files Action in order to be sure to be using the latest version, but the problem still persists.
Here is my settings:
{ "country": "es", "appFolders": [ "xx", "xx1", "xx2" ], "testFolders": [], "repoVersion": "24.6", "bcptTestFolders": [], "CICDPushBranches": [ "main", "test" ], "versioningStrategy": 16, "CICDPullRequestBranches": [ "main", "test" ], "DeployToMy-MXSandboxTest": { "EnvironmentName": "MXSandboxTest", "Scope": "PTE", "continuousDeployment": false, "SyncMode": "ForceSync" } }Thanks in advance for your help, it is really appreciated.
Best regards.
The text was updated successfully, but these errors were encountered: