I discovered Vorto yesterday, read a few docs and watched the uHangout. It is precisely what I was looking for to help with a current site. Thanks for writing and sharing this project.
The site also has a 'product catalogue' section which I'd like to build with CMSImport (discovered it this morning).
When importing with CMSImport I couldn't find any access to the Vorto language values in each field - just the field as as plain textbox. Do you know of a way to make CMSImport work with the Vorto language fields?
I looked at the .cmsPropertyData table in the umbraco DB and see the format of the dataNtext value for the Vorto entry is formatted:
I looked (briefly) at the VortoPropertyEditor.cs source, but could not determine if the dtdGuid is a fixed value for each field type. What is the dtdGuid value?
For fun I added an additional column to the source datatable and put in the {"values"...} field above and then tried to import with CMSImport - it worked. I could write a script and make an intermediate .xlsx file from the source database, building multilingual fields to match the format used by Vorto in the dataNtext field and then importing the .xlsx with CMSImport - but don't know exactly what the dtdGuid value is and if/when it changes.
I don't actually know that much about CMSImport, so can't really offer any guidance myself, however, I have asked Richard (who wrote CMSImport) if he could offer some assistance when he has a moment.
Yes a bit of a problem when you are importing data using more intelligent property editors. Same goes for ArcheType etc. It's a property editor that contains more property values and you can only map one.
So the approach you took will work indeed. Only thing is that you need to check it for every property. That is where the GUID kicks in. That describes the property editor that the field is using.
Just check them for each field and update the excel sheet for each property then all should work. If you want a more generich aprouch you can use a Field provider http://www.richardsoeteman.net/2013/12/05/FieldProvidersInCMSImport25.aspx that transforms the data coming in to the required format on the fly. But is a bit more complex since you need to check the selected prevalues to see which field (GUID) Vorto is mapping to.
Hope this makes a bit more sense and if not please let me know.
which imported without any problems. There were only 4 languages which could have been hard coded but with future scalability in mind I created an array and looped through it for each item.
Be sure to get the string format and dtdGuid correct for the datatype.
Vorto with CMSImport
Hello Matt,
I discovered Vorto yesterday, read a few docs and watched the uHangout. It is precisely what I was looking for to help with a current site. Thanks for writing and sharing this project.
The site also has a 'product catalogue' section which I'd like to build with CMSImport (discovered it this morning).
When importing with CMSImport I couldn't find any access to the Vorto language values in each field - just the field as as plain textbox. Do you know of a way to make CMSImport work with the Vorto language fields?
I looked at the .cmsPropertyData table in the umbraco DB and see the format of the dataNtext value for the Vorto entry is formatted:
{"values":{"en-US":"testing","de-DE":"testing german"},"dtdGuid":"a4b4a4d2-44db-4ce4-ad94-47da72b30242"}
I looked (briefly) at the VortoPropertyEditor.cs source, but could not determine if the dtdGuid is a fixed value for each field type. What is the dtdGuid value?
For fun I added an additional column to the source datatable and put in the {"values"...} field above and then tried to import with CMSImport - it worked. I could write a script and make an intermediate .xlsx file from the source database, building multilingual fields to match the format used by Vorto in the dataNtext field and then importing the .xlsx with CMSImport - but don't know exactly what the dtdGuid value is and if/when it changes.
Thanks for any help or advice you may have.
BR, Steve
Hi Steve,
I don't actually know that much about CMSImport, so can't really offer any guidance myself, however, I have asked Richard (who wrote CMSImport) if he could offer some assistance when he has a moment.
Hopefully he will be able to help.
Many thanks
Matt
Hi Steve,
Yes a bit of a problem when you are importing data using more intelligent property editors. Same goes for ArcheType etc. It's a property editor that contains more property values and you can only map one.
So the approach you took will work indeed. Only thing is that you need to check it for every property. That is where the GUID kicks in. That describes the property editor that the field is using.
Just check them for each field and update the excel sheet for each property then all should work. If you want a more generich aprouch you can use a Field provider http://www.richardsoeteman.net/2013/12/05/FieldProvidersInCMSImport25.aspx that transforms the data coming in to the required format on the fly. But is a bit more complex since you need to check the selected prevalues to see which field (GUID) Vorto is mapping to.
Hope this makes a bit more sense and if not please let me know.
Best,
Richard
Hi Matt,
Thank you very much for the reply and for passing the question along to Richard.
Hi Richard,
Thank you for the very helpful information. This makes perfect sense and I will try the described approach with the full recordset.
Fantastic support all around.
Best regards,
Steve
Hi Steve
How did you work out what language you were importing into?
Thanks,
Sam
Hi Sam,
I created an .xlsx using values from our source database, with fields in the format:
{"values":{"en-US":"testing","de-DE":"testing german"},"dtdGuid":"a4b4a4d2-44db-4ce4-ad94-47da72b30242"}
which imported without any problems. There were only 4 languages which could have been hard coded but with future scalability in mind I created an array and looped through it for each item.
Be sure to get the string format and dtdGuid correct for the datatype.
Hope that is helpful.
BR/Steve
Hi Steve,
I haven't actually understand exactly what I should do.
Currently, I have an import which get all property types, from SQL, just the ID and the name,
Now, I am mapping the name of the property type to create multiple property types as nodes in the CMS backend.
Now I have converted the property type field property type as Vorto data type to support multi-lanugage.
What type of logic do I need to do in the cmsimporting event in order to get it working, please?
thank you for your help.
Any ideas or comments please?
Kind Regards
is working on a reply...