You’re offline. This is a read only version of the page.
1,646
Hi All,
I did customization on the sandbox instance, The customization is when someone creates a new record on the Custom created owner table the same values inserted on the dimension of owner [Values inserted would be Code and name from the owner table to owner dimension values]. This customization works perfectly on all the sandbox instance but however it is not working on the production instance. I have deployed the same latest extension on the production instance. what was the problem? could anyone tell us why the functionality not working on the production instance?
Hi, have you generated or updated the permissions file? This is not required in Sandbox but is required in production
More details:
New command to generate or update AL permission set
Hope this helps.
Thanks.
ZHU
Hi,
Did you try to put the specifically permission on that codeunit?
Thanks
Hi Nitin Verma ,
I have check permission set and it works for one dimension but not work for another dimension.
When you try to run the code in your production environment are you using licensed user or a CSP user?
Are your code using job queues during the execution or is it all done in a trigger or a event?
Hi,
Can you check if required permission are set?
Thanks.
hi
there could be multiple reasons why the customization is not working on the production instance:
Data differences: The production instance might have different data compared to the sandbox instance, which could result in the customization not working as expected.
Code differences: There could be differences in the code between the sandbox and production instances. Make sure that the latest code has been deployed to the production instance and that there are no errors or warnings during the deployment.
Environment differences: The sandbox and production instances could be running on different environments, which could affect the customization. For example, if the customization relies on a specific version of a library, the production instance may be running a different version, which could cause issues.
Configuration differences: There could be differences in the configuration settings between the sandbox and production instances. Make sure that the necessary configuration settings are set up correctly in the production instance.
Permission differences: Check if the user account that is being used to test the customization in the production instance has the necessary permissions to access the objects and tables required by the customization.
It's important to debug the issue by checking the logs and debugging the code to identify the root cause of the issue. Once the root cause is identified, it can be addressed accordingly.
DAniele
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,113
Super User 2024 Season 2
#2
Martin Dráb
229,918
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (