Thank you for the clarification.
So you made global parameters in Factory 1, published, then exported ARM and deployed to Factory 2.
Global parameters did not initially appear in Factory 2 after deployment. Then after manually creating and publishing global parameters in Factory 2, they disappeared a few hours later.
Hmm. I am not aware of any feature of Data Factory which would cause the disappearance by itself. However, if we can show every step is correct, and there are no other influences, then all that is left as the cause is Data Factory.
So there are 2 items to investigate:
- Why the global parameters did not appear after deployment
- Why manually created and published parameters disappeared.
For point 1, first check whether the global parameters were included in the portion of ARM template you deployed. The global parameters are not part of the main template, they are under the 'factory' folder. See images below. Link to using global parameters in CI/CD.
If the global parameters were part of the deployment and you didn't see them in the UI, you may have needed to refresh the UI. UI browser windows opened before the deployment would show old data until refreshed. The deployment process does not push updates to open browsers.
For point 2, can you tell me whether there are any other developers working on that factory?
If 2 people are working on it at the same time, they will not be aware of each other's changes until they do a refresh. This also includes if you have 2 browsers open to the same Data Factory. One publish can overwrite the changes made by the other's publish.
This allows for the case where you had a browser open to Factory 2 before the ARM deployment, and did not refresh. This browser would not have the deployment's changes, and a subsequent publish could erase the global parameters.