What's Changed

• Added record state as lookup field (allows you to map to only active records)
  • Example use case is you need to create a new record (i.e. Activity) with a relationship to a contact and you match on email address, however due to merge process you have lots of inactive old records with same email address
• Added field data type to support the use of Party List fields on Activities (and maybe elsewhere later on....)
• Added support for PartyList on Activities (only 1 entity supported in the party)
• Allows to import letter using to & from
• Added support to complete Letter & Task post create (can't set the new record status as part of create due to system/SDK restriction)
• Records are set to status:
  • Letter - Status = Completed (1); Status Reason Sent (4)
  • Task - Status = Completed (1); Status Reason Completed (5)
• This support contains a new setting (Complete Records) which is set as part of configuration and only displayed when importing an activity letter or task

Full Changelog: 2.1.9197.28124...v2.1.9303.20484

This release enables users to import statuscodes. Thanks to @mattc-ri for this improvement!

What's Changed

• Added support for Status Reasons (statuscode) by @mattc-ri in #16
• Improved docs and test data by @YesWeCandrew in #17

New Contributors

• @mattc-ri made their first contribution in #16. Thanks Matt!

Full Changelog: v2.0.9156.20290...2.1.9197.28124

Releasing version 2 of Data Import ++

Full release notes: https://andyhowes.co/introducing-dataimport-v2/

Key updates:

1. Data map saving and loading

You can now save and load data maps. This means you can spend less time importing the same file over and over.

Instead of having to ensure that every single column and setting matches each time, just map it once, save the data map and load it whenever you want to import it again. You can also use this to import the same data to multiple environments, without needing to manually redo the mapping.

2. Better logging

Logs now also get produced in a table format with one row for each row in your import file. This makes it easier to work out which rows have failed and why. It also splits out information to make it more readable so you can see at a glance what kind of update occurred and the GUID of the record.

3. Import row selection

I regularly wanted to test my import on just the first few rows before running it on the remainder. Now I can!

Select only the rows that you want to import and import them. If all looks good, you can update the number of rows and do the rest.

4. Data entry speed improvement

Previously, you had to select the process fields button to show the fields to map a lookup or an option set. Now when you map a field to one of those types, it automatically shows those fields so you can use them.

This makes it faster to map a file for import.

5. UI improvements

Honestly this is my first C# app so using Visual Studio Design was a new experience. I changed the layout of the app from being SplitContainer based to a Table, which made it way more responsive to size changes, easier to work with and fixed some issues with the size of option sets.

6. Bug fixes

I also fixed a number of bugs:

• Changed the default option to “Keep data on CRM” when importing a blank field
• Added the ability to clear fields after mapping them
• Fixed an issue where incorrect option set choice caused the app to fail