If you have just a handful of fields it’s easy enough just to open the records and delete the extra spaces and re-save. When you run into scenarios with larger amounts of records that option isn’t so appealing. A slightly less painful method is to export the offending records to Excel, use some Excel wizardry to remove the spaces and the re-import. This approach is a bit of a pain because it’s a lot of steps and forces you to export all records because you aren’t able to directly (to my knowledge at least) do an advanced find in CRM for data where you query parameter is only a space – “Ends With <space>”
KingswaySoft to the Rescue
In the CRM Source use the updated FetchXML.
Next add a Derived Column Transformation. Take the existing field and use the “TRIM” function to remove the extra spaces.
On your CRM Destination, map the entity id and the updated value back to the original property.
And that’s it! Run the job and only records where the specified fields ending with spaces will get updated.
Special thanks to the folks over at KingswaySoft for naming me an MVP recently!