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
Hello,
We are currently using your plugin in our company. We're using BC as our global ERP and Azure as our datalake. The data from BC are exported every hour to ensure fresh data is available for users.
Recently, we've noticed that some lines are created by the plugin inside the datalake, but these lines don't exist in our ERP. After some investigation, it seems to be linked to some entries that are in a "buffered" state inside BC and not committed due to rollback reasons.(job queue failing)
Here is an example: at the end of the month, we ran the job queue "Post Inventory to G/L." The job queue finished in an "error" state because the user who ran that job queue was missing some rights to perform this action. But during the execution of this job queue, some entries were caught by the ADLSE plugin and sent to our Azure datalake. With the cancellation of the job queue, the data were not committed and were rolled back. We noticed this issue because we ran the job queue again the day after, and we found entries with the same IDs inside our datalake.
Is there a way to ensure that the data retrieved by the plugin are 100% committed?
Can this be link to tristate feature of Business central that reduce deadlock and improve performance.
We are using version 22.0.15.0 of Adlse
Thanks you in advance,
Regards,
The text was updated successfully, but these errors were encountered:
Hi @Guillaume-exo when looking up records inside the tables the data is already committed inside the table.
Maybe there is something inside the object "Post Inventory to G/L." I havew to look into that one.
Hello,
We are currently using your plugin in our company. We're using BC as our global ERP and Azure as our datalake. The data from BC are exported every hour to ensure fresh data is available for users.
Recently, we've noticed that some lines are created by the plugin inside the datalake, but these lines don't exist in our ERP. After some investigation, it seems to be linked to some entries that are in a "buffered" state inside BC and not committed due to rollback reasons.(job queue failing)
Here is an example: at the end of the month, we ran the job queue "Post Inventory to G/L." The job queue finished in an "error" state because the user who ran that job queue was missing some rights to perform this action. But during the execution of this job queue, some entries were caught by the ADLSE plugin and sent to our Azure datalake. With the cancellation of the job queue, the data were not committed and were rolled back. We noticed this issue because we ran the job queue again the day after, and we found entries with the same IDs inside our datalake.
Is there a way to ensure that the data retrieved by the plugin are 100% committed?
Can this be link to tristate feature of Business central that reduce deadlock and improve performance.
We are using version 22.0.15.0 of Adlse
Thanks you in advance,
Regards,
The text was updated successfully, but these errors were encountered: