We are facing a problem when populating custom attribute values for Data File and Data File Fields assets throug istool import and "Import Asser Values"
And our observation so far is because of the "Data File Folder" section.
1. Am able to upload "File1.csv” Data file successfully with folder created separately. so the Hierarchy is Host=>Data File Folders=>Data Files=>Data File Records=>Data File Field
2. Populated the custom attribute for "Data File" and "Data File Field Type" manually in IGC and exported the “Asset Values” files to understand the syntax I should follow to import through istools.
3. Created the Actual Files to populate "Custom Attributes" for Data File and Data File Filed with exact same format as exported from Step 2 with not having Asset ID in it.
And the error am getting is as below but no actual errors captured in the log files.:
Import Completed with failures.
An error occurred and no assets were imported. For more details, check the server logs.
Sample Data :
+++ Data File - begin +++
Name,Host,Data File Folder,Data File Folder,Data File Folder,Data File Folder,Data File Folder,Short Description,Long Description,Assigned To Terms,Labels,Stewards,Implements Rules,Governed by Rules,Test
"StandardizationFile.csv","ulvsjdd01.devfg.rbc.com","data","etl","NAS","SJD0","UMI","This is FullLoadSecPos data from MILVUS (B201) which located in MIT's HDFS RAW ZONE",,,,,,,"Test"
+++ Data File - end +++
Please advise how we could fix this problem, this is really breaking our head and I can't find any supporting document to fix this.
The folder structure for Data Files is very hard to use in identities. Try using the AssetID instead. I haven't tested for Data Files, but when this feature first became available a year or so ago ...
It is working with Asset ID, but it would be really hard to manage with Asset ID. We don't want to mention Asset ID unless it's really necessary. The coding part would be really complex otherwise.
I tried all possibilities that you have suggested but no luck.
What does the export file look like when you dump a real one...with folders, etc.. Dump one, change it's Short Description and then re-import it. Make no changes to the identity. If that doesn't ...
+++ Data File - begin +++
Name,Host,Data File Folder,Data File Folder,Data File Folder,Data File Folder,Data File Folder,Short Description,Long Description,Assigned To Terms,Labels,Stewards,Implements Rules,Governed by Rules,Test
"StandardizationFile.csv","ulvsjdd01.devfg.rbc.com","data","etl","NAS","SJD0","UMI","This is FullLoadSecPos data from MILVUS (B201) which located in MIT's HDFS RAW ZONE",,,,,,,"Test"
+++ Data File - end +++
Please see above, That's exactly I did, just that I removed AssetID field, everything else was just exported as is.
This seems to be a bug, I will have a call with IBM Support next week and see how it goes. I tried with all possibilities but nothing worked. We have the same problem for Data Field import also when having Data File Folder defined.
Try also, one more thing.....test it with just removing the value of the Asset Id field.....not the comma placeholder or its heading. Leave those in. Just in case it is an issue with the header.
...
Add To Favorites View next topic View previous topic
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
