Configuration Experiment #D1

Configuration Experiment #D1


Goal
The goal of this experiment is to help you understand how configuration changes impact transactions. For this challenge, you will use a production workspace and enter some configuration. When asked to write down something, please copy the value to a document (along with the step #), as you will be using those values later on.

Difficulty
Easy.

Preparation
Create a CSV file with the following:
  • Date,Unique ID,Owner,Revenue,Customer
  • 2021-01-01,ID-1,Daniel Martinez,100,A
  • 2021-01-01,ID-2,Daniel Martinez,100,B
  • 2021-02-01,ID-3,Daniel Martinez,1000,C
  • 2021-02-01,ID-4,Daniel Martinez,1000,D

As you can see, each record has a different Unique ID.

Steps
  1. Go to Account > My Workspaces
  2. Create a production workspace
  3. Go to Transactions > Add Transactions
  4. Import your CSV file
  5. Wait 10 seconds for the import to finish
  6. Go to Transactions > All Transactions
    1. Write down how many transactions are present
    2. Why are there 4 transactions?

  7. Go to Transactions > Add Transactions
  8. Import your CSV file again
  9. Wait 10 seconds for the import to finish
  10. Go to Transactions > All Transactions
    1. Write down how many transactions are present
    2. Why are there still only 4 transactions (no duplicates) after re-importing the same CSV file?
  11. Go to Transactions > Add Transactions
  12. Edit your CSV file
    1. Replace customer "A" by "A1" for "ID-1"
  13. Import your CSV file again
  14. Wait 10 seconds for the import to finish
  15. Go to Transactions > All Transactions
  16. Write down how many transactions are present
    1. Why are there still 4 transactions?
    2. What is the customer for "ID-1"?
  17. Go to Transactions > Add Transactions
  18. Edit your CSV file
    1. Duplicate row "ID-2"
    2. Keep all field values the same  
  19. Import your CSV file again
  20. Wait 10 seconds for the import to finish
  21. Go to Transactions > All Transactions
    1. Write down how many transactions are present
    2. Why are there still 4 transactions (not 5 since the CSV now has 5 rows)?
  22. Go to Transactions > Add Transactions
  23. Edit your CSV file
    1. Duplicate row "ID-2" again
    2. Change its Unique ID to "ID-5"
  24. Import your CSV file again
  25. Wait 10 seconds for the import to finish
  26. Go to Transactions > All Transactions
    1. Write down how many transactions are present
    2. Why are there 5 transactions now?
  27. Go to Transactions > Add Transactions
  28. Edit your CSV file
    1. Delete all rows except "ID-1"
  29. Import your CSV file again
  30. Wait 10 seconds for the import to finish
  31. Go to Transactions > All Transactions
    1. Write down how many transactions are present
    2. Why are there still 5 transactions?
  32. Click on transaction "ID-1" to edit it 
  33. Change the "Customer" from "A1" to "XXX"
  34. Save and select "Prevent Overwrites"
  35. Go to Transactions > Add Transactions
  36. Edit your CSV file
  37. Replace customer "A1" by "YYY" for "ID-1"
  38. Import your CSV file again
  39. Wait 10 seconds for the import to finish
  40. Go to Transactions > All Transactions
    1. Write down how many transactions are present
    2. What is customer for "ID-1"?
    3. Is it "XXX" or "YYY"?

Key Learnings
  • Having a field mapped to the Unique ID category ensures that
    • We don't create duplicates on re-import
    • We can update the right record after making changes on re-import
  • We do not propagate deletes on re-import
    • Deleting entries from CSV and re-importing does not delete transactions
    • This allows for incremental (partial) transaction uploads
  • It's possible to make changes within Sales Cookie and "lock" a transaction
    • Subsequent uploads cannot alter the transaction
    • The entire transaction is locked (all fields)

    • Related Articles

    • Configuration Experiment #V6

      Goal The goal of this experiment is to help you understand how to use custom variables in your configuration. For this challenge, you will use a production workspace and enter some configuration. When asked to write down something, please copy the ...

    • Configuration Experiment #D2

      Goal The goal of this experiment is to help you understand how configuration changes impact transactions. For this challenge, you will use a production workspace and enter some configuration. When asked to write down something, please copy the value ...

    • Configuration Experiment #D3

      Goal The goal of this experiment is to help you understand how configuration changes impact transactions. For this challenge, you will use a production workspace and enter some configuration. When asked to write down something, please copy the value ...

    • Configuration Experiment #V5

      Goal The goal of this experiment is to help you understand how to use custom variables in your configuration. For this challenge, you will use a demo workspace and enter some configuration. When asked to write down something, please copy the value to ...

    • Configuration Experiment #V3

      Goal The goal of this experiment is to help you understand how to use custom variables in your configuration. For this challenge, you will use a demo workspace and enter some configuration. When asked to write down something, please copy the value to ...