Issue
In version 17.5 of the Bot, we fixed the delimiter option when importing data. Previously it was ignoring the choice selected and would usually still work correctly. Now that this issue is fixed, it will not ignore the choice selected and this could give you different results.
Additional Information
After upgrading to version 17.5 of the Bot or later, if you find that your data is not being imported the way it used to, double check your data to make sure you have a specific delimiter. Then recreate the Open Data action using the correct delimiter or select the correct delimiter when manually importing. Make sure the delimiter chosen is clear and that the data is "clean."
If the delimiter in your data is not obvious, the issue with the import may be due to your data not being "clean." You may need to reformat your data.
If you have more than one character, such as a comma and a period in your data, RPA may have been choosing the comma when you thought it should use the period. This can change your outcome.
If you have any questions please feel free to reach out to Support@Nintex.com and we can assist you. Please provide a sample of the data, the desired outcome and the actual outcome along with the version you upgraded from and the version you are currently using.
