So I've been trying to get this XML import thing to work, but despite everything I can find online, I cannot get a simple Import rule to work!
Is there some additional setup I am missing? I have an import rule pointed at a folder and I tossed an "import.xml" file into the folder and the same coding used in the examples and nothing happens.
I know this might be a simple problem I'm overlooking, but thanks for any feedback!
Hi Tim,
Thanks for the reply! It looks like you may be missing a link to the thread you are referencing above though. I've posted my xml file below. I've been following the examples in the pdf and posts on threads like this: https://forum.solidworks.com/message/390669#390669.
I simply cannot get EPDM to import the xml file into the SQL database. I made an import rule to look in a folder and placed an XML into it, but absolutely nothing happens. I've been looking into if there is some additional setup needed, but it just looks like I need an Import rule pointing to a folder and it should work...
<?xml version="1.0"?>
<xml>
<transactions>
<transaction
date="1196854268"
type="wf_import_document_attributes"
vaultname="Sandbox1">
<document
aliasset=""
pdmweid="0"
idattribute="PEC_ECN_No"
id="000033"
idcfgname="">
<configuration name="">
<attribute name="CAD_Material" value="TEST"/>
</document>
</transaction>
</transactions>
</xml>
Just for reference:
Yes, that was the thread I intended to post for you. Was tired, thanks.
Does the xml file disappear?
It does not, which is my problem.
Your xml file is missing the closing bracket for configuration. Copy this into your xml file and try it. I bet it works
<?xml version="1.0"?>
<xml>
<transactions>
<transaction
date="1196854268"
type="wf_import_document_attributes"
vaultname="Sandbox1">
<document
aliasset=""
pdmweid="0"
idattribute="PEC_ECN_No"
id="000033"
idcfgname="">
<configuration name="">
<attribute name="CAD_Material" value="TEST"/>
</configuration>
</document>
</transaction>
</transactions>
</xml>
Try this one. Yours is missing the attribute id=1, 2, 3, 4, etc.
<?xml version="1.0"?>
<xml>
<transactions>
<transaction
date="1384361754"
type="wf_import_document_attributes"
vaultname="_epdmTestbed">
<document
aliasset=""
pdmweid="0"
idattribute="<the variable name to search files for>"
id="<with a variable value matching this value>"
idcfgname="">
<configuration name="">
<attribute id="1" name="Cost" value="4.27"/>
</configuration>
</document>
</transaction>
</transactions>
</xml>
You have the import folder as "C:\" is that "C:\" of the machine that is running the database service (not of the client)? Typically I use a UNC path there.
Jeff is right but also Jeff, I use a local folder on the server while in testing and the c:\<path>\xml_imports works for me.
Still no resoution on the multiple variable problem I'm still having. We are close though.
Sorry guys, but still no dice. Neither the updated xml or updating to a UNC path worked.
The XML file is still sitting where i left it
Here is my data import setup. For testing I use the local drive on the server. Once I get that going, will use the UNC name.
Pardon for asking, but are all SQL Server & archive server services running?
I've got the exact same situation, but nothing is happening.
And I have no idea how to even check if the SQL server & archive server services are running.
If you are able to navigate through the vault, then they are running. If not, do you have an SQL server DBA who manages your SQL?
The only access to the vault I have is through the local view I created... I'm assuming your refering to navigating through the vault on the actual server, not my local view, which means I'm going to have to get back to you once our IT guy gets in next week.
Yes. On the server. I suspect that is exactly your xml is not working.
The server needs access to the "exact" folder where the xml is being imported using the data import rule and the server cannot see your local disk unless it is a UNC shared path.
You can try sharing the local disk folder so the server has access to it but you'll need IT for that so I don't hold out hope of it working.
Let's pick it up Monday.
Tim CEPA
Tim,
I finally tracked down someone who has access to the SQL server database, but we do not have a SQL admin. I am now able to log into the vault server and have access to SSMS, but have no idea where to go from there.
Any advice?
So... anybody got any suggestions?
Hi Michael, I take it your database is on a different machine then the client? If so, check the application log on the machine with the database server. (I always check the client error log on the local machine and the application log on the database server machine) Typically the issue is an inability to connect to the database server. (This happened to me recently - the client could not connect to SQL) To test whether you've done everything else correctly, install SQL Server, database server and archive server on the local machine and test. If it works locally, you know it's a communication error. Regards, Joy
Thanks for the reply Joy!
That's a great idea! I didn't even know it was possible to have another SQL, database and archive server installed locally. I'll definately research this and give it a try.
Verifing the correct "vaultname" in the XML file worked for me.
My issue was resolved by ensuring the datacard variables that will be updated during the XML are mapped to SolidWorks custom properties. Without this, it won't work. You may be experiencing a different issue but wanted to update the thread with my solution.
Tim CEPA
What specifically is not working Michael?
Copy the xml file directly from the help? I am experiencing a problem with this system as well. Check out this thread where we have shared a lot of background information and see if your problem is the same.
Tim CEPA
http://www.equivaq.com