Hi John,

What are the aliasses for these pickers? I think it should just work but it's checking based on nodename.

Cheers,

Richard

thanks for the quick reply.

.example : person listing

Person - person 1 - person 2 - person 3

in the picker..

I need to input exact nodename in my excel file

"person 1, person 2 , person 3" ??

Regards, JohnR

Hi John,

Yes then its should find the references.

Best,

Richard

Hi Richard ,

One thing ..so if i got multiple site.with many content picker..i should create custom data type for each content picker?

thanks

Hi John,

No it's per Property editor type so you should only need one.

Best,

Richard

Hi Richard,

I mean if the other fields had their own specific startnode .

Category 1 List <- picker 1

Category 2 List <- picker 2

Thanks

Ehh then yes but if the picker is supported with CMSImport it checks for the correct rootnode.

ahh . okay thank you for the reply richard.

good day richard,

Cms import also supports range picker ?

MM/DD/YYYY h:mm:ss - MM/DD/YYYY h:mm:ss

-john

Hi John,

Range picker is not a supported property editor. What you can do is either make sure the datasource contains exactly the required format or write a Fieldprovider that transforms the data in the correct format.

Best,

Richard

Thanks Richard.

I've encountered an error in CMS import when i upload content that was map to a content picker.

It work fine with setting up the startnode but when i used another way the xpath it caused error when i'm uploading . I check the field in the website . Its working it shows the list of content that i was expecting. When i used cms import this will show

Error while importing data for property 'docu alias', datasource record Name = 'SampleName, Error :Expression must evaluate to a node-set.

Hi John,

Xpath is indeed harder to determine than the normal mapped id. What is the xpath you are using? Maybe I can improve the algorithm for that.

Best,

Richard

Hi Richard,

This one $site//Persons .

Regards, JohnR

$site gets replaced with // so I think the xpath will be ////persons in your case and that's not ideal indeed.

In case you are intrested to test. I've just added that fix to the next version of CMSImport

Best,

Richard

Hi Richard,

I think its working now ..

Nice2x. can we get this version in unlimited license?..

Also i want to know what other fixes or new features you got in the new version..

Cheers, Juan

Yes this version will be a next version so included in the normal package. Release notes will be added after release

When be the release for the new version ?

short after 7.3 I think

ahh i see.

So it is possible that we used the new version you send to me and purchase the license. To be able to used the fixed xpath .?

Hi John,

Yes that would work. It's just the normal package only you got it earlier than the release date :)

Best,

Richard

Great!

hi richard,

the sorting of the data that was import was based on what ?

Is it there node name or the publish date?

cheers, JohnR

Based on first found.

is working on a reply...