It’s the D100 training for 2020R1, and it’s in the documentation…
Here is a browsable list - to get the appropriate build to match your version.http://acumatica-builds.s3.amazonaws.com/index.html?prefix=builds/zip/salesdemo/2021r2/
@PRapnikas OMG - I’ve been staring at that data for a year. Thank you.Using a combo of that data and unprocessed rows - a business event could probably be built for email notifications.
@PRapnikas Thanks for the super detailed update! I poked at that same exact setup for multiple hours - and could not get it to work “consistently” - but the way you explained it would account for the inconsistent behaviors I was seeing. I’m going to revisit this!I’m curious as to “where” Acumatica is storing what revisions have been imported/processed - I will look at this. Import Scenario + File Sync functional gaps:A scheduled import scenario with file sync enabled does not trigger the file sync. It needs to be scheduled separately. Since the file sync needs to run before the import… humans need to manage the automation schedules to ensure they execute in the right order. No out of the box error notifications if scheduled import fails. It’s doable but needs to be constructed using GI’s against the Process Import Scenarios DAC, with a business event. No error notifications if the file sync fails. If this happens, then the import scenario will still run and re-import the same revision
Here is my problem. I can successfully run the import scenario with a single file, but how do I do it for multiple? When I perform the “File Synchronization", I end up as multiple versions (one for each new file). How do I configure Acumatica to execute my IS nightly and to import all the new files it finds? @PRapnikas - I understand your problem. The testing and research I have done shows that it does not support processing “multiple revisions that have not been imported”.There are multiple functional gaps in the import + file sync functionality. It’s not usable for business critical automation of data imports like importing orders from external systems.Import Scenario + File Sync functional gaps:A scheduled import scenario with file sync enabled does not trigger the file sync. It needs to be scheduled separately. Since the file sync needs to run before the import… humans need to manage the automation schedules to ensure they execute in the right order. No out of the box error not
Pending review - Business Events - Add Subscriber Export Scenariohttps://community.acumatica.com/ideas/business%2Devents%2Dadd%2Dsubscriber%2Dexport%2Dscenario%2D1379
Hey-Yes, triggering an export scenario - same need here. Trying to look for ways to accomplish this without code.Here is an example of how to export the file! -Chad
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.