This content has been marked as final. Show 2 replies
What is the condition that you want to test for?
We have had clients where we did a lot of pre-validating of the source files before importing to FDM, we handled that in the custom batch script created to launch the batch engine, e.g.
1. Check file header for ceratin conditions
2. Check record count matches control total
3. Check period exists in the file
4. Check TB balances per entity
We dropped the files into a 'SourceFiles' folder and they were only copied in to the OpenBatch folder if they passed all the pre-tests, that way only files we knew were in the correct format were attempted to process.
It also meant that we could easily distinguish issues with the source file from issues with the mapping logic.
Hope this helps
Thanks for the feedback, I follow your point... I might approach it that way.
My source file is 500k records, so I've chosen to query the corresponding TDATASEG# table post import event because it's quicker than reading into an in-memory recordset. The sum I run on the corresponding TDATASEG# table runs in 5 seconds. I'm running the checksum in the Import Action.