This functionality is not built into EPDM, but an add-in program can be written to accomplish this. I found an example in the API section but based on some of the comments I'm not sure if it still works. Would be a good starting place however.
API is out of my skillset right now but we do have a programmer who may be able to work some magic. If our Sage consultant can work with an XML file then maybe that would be a better option as mentioned in Brians post. The CSV format was what the Sage consultant requested though for initial testing.
Michael, I made the download and it's working with VS 2015 and EPDM 2015 Service Pack 2.1.
You helped me a lot!
I have not done it myself, but isn't that the purpose of Export Rules?
It has a lot more options than the csv export. They can be run on a Workflow Transition.
Most ERP systems can read xml I am told.
Would be interested to hear about your progress if you go that route.
You can also investigate the generation of a parameter file using the default dispatch addin that comes with EPDM. It would be possible to do this at specific intervals and you can generate a *.csv file in this fashion at a specified folder location
Just make sure the folder location is accessible from all machines running the dispatch script. Your VAR should be able to help (lol...that would be me / Joshua)
One thing that still has me wondering. What BOM will be automatically exported from which assembly file? I imagine we would require one BOM to be exported from the Top level assembly of the dataset which is being approved. Is this how the export works?
Until now we manually exported a BOM from a specific assembly, with an automated procedure how do we know what content will be in the export?
Wayne, my understanding is that the selected file's BOM will be exported, not all files passing the transition
In other words:
- If you are transitioning an assembly, the assembly BOM will be exported.
- If you are transitioning a bunch of part files (and the rule is specified for files), all file BOM's will be exported individually
So which ever file is highlighted at the time of Modify -> Change state -> Those files will have their BOM's exported (filtered by the condition in the Actions section of the workflow transition)
In the end, with the help of our VAR we are using XML export on transition to released state
i would like to discuss over the phone this with you if possible. I am in a very similiar situation and you may be able to save me from heading down a wrong path.