0

Import asset- and workorder data

Dear all,

I have succesfully imported asset data before with the import function. Now I've tried to expand this import and also added some data I need in the workorder of the associated asset. I've found that the mechanism doesn't imports this data. Is this the way the import works or am I overlooking something?

This is my import definition:

JobNumbers.cJobOrderNumber - Imported OK

AssetEx.cField1 - Imported OK

Assets.nManufacturerUID - Imported OK

Assets.cModelNumber - Imported OK

Types.nManufacturerUID - Imported OK

Types.cModelNumber - Imported OK

Types.cDescription - Imported OK

Assets.cSerialNumber - Imported OK

Assets.nFacilityUID - Imported OK

Addresses.nFacilityUID - Imported OK

Addresses.cAddress1 - Imported OK

Addresses.cCity - Imported OK

Addresses.cCountry - Imported OK

Addresses.cType - Imported OK

Addresses.cPhone1 - Imported OK

CallSheets.tMaintDate - Imported OK

CallSheets.nJobNumberUID - Not imported

CallSheets.cContactInfo - Not imported

CallSheetEx.cField1 - Not imported

 
 
Many thanks
 
Frank

14 comments

Date Votes
0
Avatar
Mike Milcke

Dear Frank,

I have verified that the three CallSheets fields in question are supported. To troubleshoot why the data isn't coming through, can you provide a data sample? Which version are you using?

 

Mike

 

 

0
Avatar
Frank Becks

Hi Mike

Attached is the data I've tried to import. I've saved the csv as txt because it wasnt allowed to upload.

I'm currently using version 2.05 of MET/TEAM.

 

Frank

Attachment not imported: delivery.txt
0
Avatar
Mike Milcke

Hi Frank,

Using MET/TEAM 2.0.5, I took your definitions, made a file out of them, added "MET/TEAM" as the first line and imported it into the definition screen. I imported your data file and it looks like the three fields populated correctly.

Maybe double-check that the fields line up correctly with the definitions, I don't know what else the problem may be...?

Mike

 

Attachment not imported: import-log.txt
0
Avatar
Frank Becks

Hi Mike

Good news that this is possible :)

Can you please send me an extract of the import definition talbles you are using and a screenshot of the import setup? Because I've tried it again from scratch and had no succes. 

Many thanks.

Frank

0
Avatar
Mike Milcke

Hi Frank

Attached are two screenshots and the extracted defintions. Since your data file has headers, I'm skipping 1 row when running the import. The version I used is 2.0.5.8.

 

Mike

 

Attachment not imported: def.txt
0
Avatar
Frank Becks

Hi Mike,

Very strange. I'm also on 2.0.5.8. I recreated the definition again from scratch same as in def.txt above. Used the same data file I sent you. The import log looks the same (import_log.odt). But the fields job number, contact info and ex 1 aren't filled on the callsheet (2015-10-06_22.57.54.png). Can this be because this is the trail version? 

Frank.

Attachment not imported: 2015-10-06_22.57.54.png
0
Avatar
Mike Milcke

Hi Frank,

I agree, this makes no sense. At this point I would look at the database, to see the raw data. Do you have access to SQL Server via SQL Server Management Studio (SSMS)? I would look at the fields that aren't populated on screen.Select the metteam database and open a new query window. You can determine which data came from which import by looking for the import via SELECT * FROM Imports and tying the nImportUID value to the data query, i.e. SELECT * FROM CallSheets WHERE nImportUID = xyz and SELECT cField1 FROM CallSheetEx WHERE nImportUID = xyz, where xyz is the nImportUID of the import you want to investigate.

 

Mike

0
Avatar
Mike Milcke

Hi Frank,

If you can ftp the zipped up database (I don't think it could be attached), I can take a look at it. One more thing you could do is look at the MET/TEAM log files for any errors. I'm a bit puzzled by the idea that one or more fields would fail to import with an error and the rest coming through - aside from that I would expect the error to appear in the import log itself. But if nothing else, it may instead reveal a problem with displaying the imported values on the work order page, if that is the problem instead. The logs are in C:\inetpub\wwwroot\METTEAM\Logs.

 

Mike

0
Avatar
Frank Becks

Hi Mike

I've tried accessing the database with the management tool but didn't came far. I have uploaded the zipped database to a shared folder, maybe you can have a look?

https://drive.google.com/folderview?id=0Bw2yLi8MO71JfmlMV095ZzczSWVtZy1UY00wOVE2NGxHUVNyMzl6NnM0WXoybml6bTBkdXM&usp=sharing

There have been imported some more assets with the same import definition today, got the same import log as you did, but again no data was populated on the asset's worksheet. I've also checked the Logs directory but there wasn't any indication of errors due to the import in today's log.

Frank

0
Avatar
Mike Milcke

Hi Frank,

I was able to download your mdf, but I can't use it without the log file (*.ldf). Normally backing it up rather than copying is easier (SSMS, All Tasks -> Backup), but if you can upload the ldf like you did the mdf, maybe that will work too.

 

Mike

 

0
Avatar
Frank Becks

Hi Mike, 

I've uploaded all Idf (and mdf) files to the shared folder.

Kind regards,

Frank

0
Avatar
Mike Milcke

Hi Frank,

This time I was able to attach the database, thank you. I'm running this query in SSMS:


SELECT
    tMaintDate, cJobOrderNumber, cContactInfo, cField1, cs.nCallSheetUID
FROM
    callsheets cs
LEFT JOIN
    dbo.CallSheetEx csx ON cs.nCallSheetUID = csx.nCallSheetUID
LEFT JOIN
    dbo.JobNumbers j ON cs.nJobNumberUID = j.nJobNumberUID
WHERE
    cs.nImportUID IS NOT NULL

The results are attached. I can't tell if there is anything missing since I don't have your complete data file, but it looks pretty good, in the sense that there is data in all the fields mentioned.

How does it look to you?

Mike

Attachment not imported: results.txt
0
Avatar
Frank Becks

Hi Mike,

Thank you for for the query. I made a new CSV file to import containing 4 assets. I did some trails found that after the import the 4 assets where loaded OK with the delivery number correctly populated in all 3 fields. As a next step  in my normal workprocess I received the assets. This is when the problem occurs. The program creates 4 new assets, missing the delivery number data. See attachment for a screenshot "imported assets after receing.png". The 4 initial worksheets with all imported delivery number data have status closed and the 4 new get status received.

Is this there a way to give the inital workorder status received?

 

Frank

Attachment not imported: imported_assets_after_receiving.png
0
Avatar
Mike Milcke

Hi Frank,

If you're planning on receiving the assets after import, don't bring in the Work Orders (CallSheets records) via the data. Imported Work Orders are set to "Closed" by default, if you want to import them as "Received", incude the cCallSheetStatus field in the definition and in the data file set the column to "Received". In that case also include the lActive column in the definition and in the data set the column to -1. That way, they should appear when you search for Work Orders after the import. The reason for them being Closed and inactive by default is so that you can bring in historical data without having to then close each one manually.

 

Mike 

Please sign in to leave a comment.