Hi everybody,
Could someone help me understand why the “type fees” dimension was not updated, even though I selected “delete all items” for my transaction during the load from the Azure SQL table?
Many thanks,
Solved
import update
- Apprentice Author
Best answer by Chahat
Hi
- Whenever a new type fees will come, if the toggle (for that mapping) says “Automatically create new items” , then the type fees Dimension list will be updated automatically. | Refer image below
- “Clear items prior to import” : It will clear/blank out the transaction list entirely and then will update the Transaction list based on import configuration.
- “Clear items prior to import” : Looks like you have applied it on the transaction list, hence dimension list of “type fees” will not automatically remove those “type fees” which no longer exist in any of the rows of the Transaction List > “Type Fees” column
+18- Master Helper
- Answer
Hi
- Whenever a new type fees will come, if the toggle (for that mapping) says “Automatically create new items” , then the type fees Dimension list will be updated automatically. | Refer image below
- “Clear items prior to import” : It will clear/blank out the transaction list entirely and then will update the Transaction list based on import configuration.
- “Clear items prior to import” : Looks like you have applied it on the transaction list, hence dimension list of “type fees” will not automatically remove those “type fees” which no longer exist in any of the rows of the Transaction List > “Type Fees” column
- Employee
Hey
If you still have any open questions, feel free to submit a support ticket. We will be happy to review your transaction list and import configuration in more detail before advising you further.
- Apprentice Author
Thank you for your feedback.
In fact, the “Clear items prior to import” option does not completely delete the transaction list.
For example, when the line with -96,000 above was updated in the Azure DWH table with Type Fees = “Autres...”, this change was not reflected in Pigment after the import.
Do you know why this might be happening?
I assume that Pigment is configured to update existing rows, so this should not be a merge logic issue.
What I am trying to achieve is to completely clear the transaction list before re-inserting all the data from the DWH.
Thanks ,
Log into the Pigment Community
No account yet? Create an account
Single Sign-On Need help?
Log in with your Pigment accountEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.