I work with the CMS Import 3.7.3. Now I tried to import some data as contet.
After asign the fields from the CSV to the content properties, I get the following ErrorMessage:
Now I have one question: Can it be, that it is, because I use the obsolete MultiNode Treepicker?
Becase I used a Documenttype for the Import, which don't have this obsolete Picker. And it worked. Then I added a new MultiNode Treepicker and it also worked. But when I added a property with the old one, it crashed with the same error-message like you can see above!
If the problem is the obsolete MNTP, is there a workaround?
That is strange since there is nothing changed in for the legacy picker. So I am affraid this is something that is changed in the latest umbraco version.
But why are you using legacy instead of the new pickers?
NullReferenceException during Import
Hi!
I work with the CMS Import 3.7.3. Now I tried to import some data as contet. After asign the fields from the CSV to the content properties, I get the following ErrorMessage:
Here the ErrorMessage in english:
Does anybody has an idea?
HI Looks like it can't read any pre values from the database. Are MNTP prevalues stored correctly? No errors when opening or save the datatype?
Best,
Richard
Hi! I don't fill any of the MNTP with cms-import. Only Name, Title and Text (RTE). When I save the Page via Umbraco - everything is fine :)
Saving the page is something different than MNTP ;-) MNTP prevalues is throwing the error. SO must be something related to that.
Now I have one question: Can it be, that it is, because I use the obsolete MultiNode Treepicker? Becase I used a Documenttype for the Import, which don't have this obsolete Picker. And it worked. Then I added a new MultiNode Treepicker and it also worked. But when I added a property with the old one, it crashed with the same error-message like you can see above! If the problem is the obsolete MNTP, is there a workaround?
That is strange since there is nothing changed in for the legacy picker. So I am affraid this is something that is changed in the latest umbraco version.
But why are you using legacy instead of the new pickers?
Best,
Richard
Hi,
I went through all DataTypes and save them. Now the mostly "pre-value"-warning disappeared in the log. And the import worked!
is working on a reply...