Question to all who may know; we are trying to import files (XML) into DataPage VIA flash-drive from another source, can anyone explain to me how to do so.
The data importer tool running on your equipment sends the data to the SQL database, there should be a folder for the xml files named something like ForStatsFiles, copy them to this location for import. There are a number of ways it could be set up.
Open data importer settings, you'll see "path to monitor". You can drop files in that folder or set it to the folder you are using and import that way. Or in datapage+ under tools/import data you can use the data import wizard.
This is assuming you are using datapage+ but you have not stated which datapage you are using.
Yes, we are using DataPage + 5.0; we tried to use import data within datapge but are given errors. I'm thinking whatever the file is maybe the format (layout) is not how it should be that datapage can not understand / see it; does this make any sense?
It has to be a format/layout issue but without seeing the file we would all just be guessing. I myself have only played with dumping xml from datapage+ and importing it back in just to try it out. If you feel comfortable posting one of the files I'd be glad to try and figure it out.
Yes, we are using DataPage + 5.0; we tried to use import data within datapge but are given errors. I'm thinking whatever the file is maybe the format (layout) is not how it should be that datapage can not understand / see it; does this make any sense?
That makes sense to me, and I am going through the same issue. What machine are you getting the xml file from?
We took information from another source other than our PC-DMIS and tried to see if DataPage could open it. This data was on a flash-drive as an XML file but I'm thinking there must be an issue with the layout of the data (format), DataPage may need it in a format (layout) to see it even though the file is XML.
The xml file from PC-Dmis to Datapage+ is specific to this software. The only way I have done this is to import .csv files and this requires mapping of the relevant fields (customise option) for the first file imported and it then remembers the format for future files. This was taking data from a Tesascan. Please bear in mind that your file must have a part name, dimension name, nominal + and - tolerances and the actual value for it to work and import successfully into the SQL database.
