Hi guys,
I was wondering of anyone could help through the process of creating and importing an XML file to which EPDM will import please? I cant seem to find any documentation which tells you how to create an xml file for EPDM to then import. Also how does EPDM then add future imports to the list or does it just replace the list?
Also does it have to be an XML can it be a csv file? As I have managed to create a list as a csv.
Thanks
Hey Scott,
For importing XML into PDM to update PDM datacards, take a look at this thread. There are a few gotchas but it works well. Yes, it has to be an XML file, not CSV. This process is used for updating datacard fields only, not creating new documents.
Here's the general idea: The XML import updates files in PDM after they have been used to create a part/item master in your ERP system first. The ERP is basically sending updated BOM data back to part master files in PDM so they stay synced.
PDM reads the XML file and searches PDM for a document with a datacard variable named the value of the "idattribute" tag and has a value of the "id" tag, then updates the all variables indicated under the <configuration name=... tag.
Use alias sets to map PDM variable names to your ERP variable names so you can simply do a raw XML export from your ERP without worrying about converting variable names.
PDM variable "Cost" = ERP variable "material_cost"
PDM variable "Material" = ERP variable "material_name"
PDM variable "Finish" = ERP variable "material_finish"
Also, here's the basic layout you need for each incoming XML file. This XML will do the following:
Caution: PDM will only update those datacard variables under the <configuration name=... tag if they are mapped to SW custom properties.
<?xml version="1.0"?>
<xml>
<transactions>
<transaction
date="1384361754"
type="wf_import_document_attributes"
vaultname="your vault name">
<document
aliasset=""
pdmweid="0"
idattribute="PDMDocID"
id="2808015"
idcfgname="">
<configuration name="enter the configuration to find">
<attribute id="1" name="Cost" value="4.27"/>
<attribute id="1" name="Material" value="ABS-PC"/>
<attribute id="1" name="Finish" value="Bead Blast"/>
</configuration>
</document>
</transaction>
</transactions>
</xml>
To ensure I don't end up updating the wrong file by searching for a datacard value that "might" get duplicated, I wrote an add-in that grabs the PDM DocumentID and updates the datacard field "PDMDocID" with the PDM DocumentID from the database so the file is truly unique according to the ERP and can be easily tracked and searched with in PDM. I use it for my own needs and give it away free to our clients who sign up for our monthly PDM consulting subscription.
Good luck.
Tim CEPA
Believe in The Q!