I'm working with a legacy v616 site that has a CMS Import 3.0 process already set up. It has something I haven't seen before which is a column that includes the nodeId for the parent ID which is being imported. There was a template XLS and some detailed instructions to follow. Naturally this is crazy urgent.
Everything appears to be straightforward with the mappings. However when I run it fails with this error message:
Error while importing data for property '', datasource record NodeName + URL = 'tokyu-hands', Error :A parameter passed into a method was not a valid value Parameter name: parentId
This does not appear to match any of the mappings. I'm not sure what this parameter name parentId may be referring to.
I tried to separate the import into single sheets for each node so that no recursive import is used but I still get this error.
May it be that some custom import logic has been added that I can remove somehow or does this error suggest anything else to you that I could investigate?
EDIT TO ADD:
I tried to make this much simpler and remove the parent ID and just separate the spreadsheet into a different file for each parent node.
I'm getting a very different error now.
Where the Excel source has a date in the following format:
"2016-04-01"
I've added a format as "dd-MM-yyyy" but this keeps returning the error:
Error while importing data for property 'contentStartDate', datasource record NodeName + URL = 'tokyu-hands',
Error :2016-00-01 is not a valid DateTime value
Only uploading a single line as a test, really not sure why it can't read the month correctly.
The date format is always difficult :-( Sometimes Excel shows the format in excel but the real file contains a different format. Did you use any formatting on the advanced field settings? If not have a play with that because the date shown in the error message is invalid indeed.
thanks Richard in the end it worked.
I copied and paste special the format of "dd/MM/yyyy" into the date columns in the spreadsheet, and then (counter intuitively) set the date format import to MM/dd/yyyy and it imports successfully.
So there you go, I'm sure that's just excel being weird about dates.
It's a very old version of CMSImport now so not much to worry about.
cms import 3.0 legacy site
I'm working with a legacy v616 site that has a CMS Import 3.0 process already set up. It has something I haven't seen before which is a column that includes the nodeId for the parent ID which is being imported. There was a template XLS and some detailed instructions to follow. Naturally this is crazy urgent.
Everything appears to be straightforward with the mappings. However when I run it fails with this error message:
This does not appear to match any of the mappings. I'm not sure what this parameter name parentId may be referring to.
I tried to separate the import into single sheets for each node so that no recursive import is used but I still get this error.
May it be that some custom import logic has been added that I can remove somehow or does this error suggest anything else to you that I could investigate?
EDIT TO ADD:
I tried to make this much simpler and remove the parent ID and just separate the spreadsheet into a different file for each parent node.
I'm getting a very different error now.
Where the Excel source has a date in the following format:
"2016-04-01"
I've added a format as "dd-MM-yyyy" but this keeps returning the error:
Only uploading a single line as a test, really not sure why it can't read the month correctly.
Hi John,
The date format is always difficult :-( Sometimes Excel shows the format in excel but the real file contains a different format. Did you use any formatting on the advanced field settings? If not have a play with that because the date shown in the error message is invalid indeed.
Best,
Richard
thanks Richard in the end it worked. I copied and paste special the format of "dd/MM/yyyy" into the date columns in the spreadsheet, and then (counter intuitively) set the date format import to MM/dd/yyyy and it imports successfully. So there you go, I'm sure that's just excel being weird about dates. It's a very old version of CMSImport now so not much to worry about.
Great to hear it's solved John!
is working on a reply...