Sage 100

Has anyone been successful in running a crystal report in perform logic after a vi import. I have created a vi to import some GL journals and I need to create a text file to report on these j/e's. I have attempted to run a batch file with a visual cut report in it. Unfortunately the import just hangs upon completion. I thinking it may be a memory issue. @alnoorcassim, Any creative solutions?

Actually I believe i have resolved my immediate issue by chaining a vi export to create the file I need.

Ok. The only problem is that you can't seem to chain an export vi from a import vi. Alnoor, Is there a behind the scenes work around because the export works great but I need to start it after the vi imports are finished.

What is the original import file? What would be different about the import file than the export file? When I import my JE's for Timeslips, my VI import renames the import file with a datestamp and moves it to an archive folder in case I ever need to reference it. Would that work in your situation?

Actually I am trying to create a results file of whether the JE's imported correctly. My export has a single line for each of the imported JE's on whether I header was imported correctly based on the journal deleted flag.

@alnoorcassim call me on this. Looks like I may need to customize the vi with perform logic or an custom interface.

@JimWoodhead - I just created an import called VEND_IMPORT and export called VEND_EXPORT. In VEND_IMPORT I chained to the export job by just typing in VEND_EXPORT. See attached pic. Then ran the import as auto-run from batch file. It is running export for me too. Maybe somebody else can confirm this too. In the end I believe the change Sage made was just to filter the Chain To lookup but not any chain-to logic.

Alnoor ... Genius for trying that. it works.