Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] - Incorrect comparison when comparing 2 Long Text Area fields between source CSV and target SF if the long text area includes the character " #788

Open
jorgesolebur opened this issue Jun 7, 2024 · 2 comments
Assignees
Labels
bug Something isn't working, looks like a bug in-progress Issue is currently in the resolution progress

Comments

@jorgesolebur
Copy link

jorgesolebur commented Jun 7, 2024

Describe the bug
SFDMU compares all fields from source and target in order to identify if there is a need to update/insert the target.
When SFDMU compares Long Text Area fields between Source = CSV and Target = Sandbox, and if the long text area field in Salesforce includes the character ", SFDMU does not correctly compare both fields. Reason been:

  • In the CSV file, the long text area field will include double character "" to represent the character "
  • In SF sandbox, the long text area field will include only 1 character " to represent the character "

This is because the character " is special, and if we want to insert the character " into a text area field in Salesforce from a CSV file, we need to put it 2 times.

To Reproduce

  • Use any Text field from any object, and configure SFDMU to do UPSERT on that object
  • Create a record in that object in SF, and fill in a value with " character. For instance 'This is character " is special'
  • Use the SFDMU export.json file to export the data from that object into a CSV file. The TEXT field used will have this value in the CSV: "This is character "" is special"
  • Run again SFDMU with source as CSV and target as sandbox. We do not expect any UPDATE as we didn't change anything anything. However SFDMU will try to update the record in SF because teh text field is different in source and target
@jorgesolebur jorgesolebur added the bug Something isn't working, looks like a bug label Jun 7, 2024
@jorgesolebur jorgesolebur changed the title [BUG] - Incorrect comparison when comparing 2 Long Text Area fields between source and target if the long text area includes the character " [BUG] - Incorrect comparison when comparing 2 Long Text Area fields between source CSV and target SF if the long text area includes the character " Jun 7, 2024
@hknokh
Copy link
Collaborator

hknokh commented Jun 7, 2024

Hello, @jorgesolebur

Thank you for reporting a bug.
I will take a look at it as soon as possible and let you know of any updates.

Cheers

@hknokh
Copy link
Collaborator

hknokh commented Jun 9, 2024

Hello,

I wanted to let you know that I am still reviewing your case and will inform you as soon as I have any updates. Due to my current time constraints, this process may take longer than usual.

Thank you for your patience and understanding.

Best regards

@hknokh hknokh added the in-progress Issue is currently in the resolution progress label Jun 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working, looks like a bug in-progress Issue is currently in the resolution progress
Projects
None yet
Development

No branches or pull requests

2 participants