I've been trying to use the Orbit One bulk import/export tool with CRM4, but I'm having some problems with the import of a previously exported set of data. The tool seems to be working find to export, save the data to a local CSV file, exit as required and put back into the tool, but when I choose to export back to CRM is shows quite a lot of errors, but I can't find a reason as to why there was an error.
I'm hoping someone on here has had some experience of using this tool.
Our goal is to use this to export a set of leads from CRM, provide to our telesales department and once edited use it again to export back to the same records within CRM.
This was supposed to be a feature within CRM4, but was taken out of the export to spreadsheet feature in the released version. Does anyone know if this is likley to change as I'd rather use the features within CRM4 if possible as upposed to an external application.
Unhide the GUID column from the exported spreadsheet, then when you import it this 'enrich data option' will appear -- steps are in the blog above. This only works with premises setups and not partner hosted.
Thanks for this, however both these options reply on an element that no longer exists in the current release of CRM4.
When it comes to importing the .csv file, on the import tool in CRM there an option to tick a box entitled:
"Enrich data by updating existing records rather than creating new records."
Looking at our this morning, this isn't available... hence the reason we looked at the Orbit One Bulk Import / Export Tool. This works fine until you come to do the import back to CRM where it shows errors, but doesn't explain what the reason for the error is.
Unhide the GUID column from the exported spreadsheet, then when you import it this 'enrich data option' will appear -- steps are in the blog above. This only works with premises setups and not partner hosted.
Apologies... I finally got around to testing this again and as you say IT WORKS. The key issue is setting the GUID column to be the same name as the entity it's updating. If you leave it the same, the option to update isn't given.
That said I do have another problem and I think this is something to do with either a SQL issue or CRM setting for the date format.
When I tried using the Orbit One application, I eventually found out the reason it wasn't updating the records and showing an error was because the date format was incorrect. This appears to be the same using this method, when I did an update and reimported a sample the import failed 51 records out of 51. On the Excel spreadsheet there's a column showing the date the contact was last reached, when importing the updated spreadsheet this will have todays date on it and it's displayed correctly, but CRM or SQL seems to think this should be in US format.
I've checked the settings on CRM and this is set to the UK format, should I be looking elsewhere?
Unfortunately, you are using an unsupported tool so the chances that someone else has specific experience with certain fields are unlikely. I recommend that you use a supported method, for updating and importing the changes to CRM. There are several available. Below is a list of examples:
