End user created a new main account / vendor / Customer / FA/ bank . Assume that using these data created some financial journals , but not posted . Now end user came to know that the data which had created was wrong . So tried to delete those master data.
An error occur: “A financial dimension value is based on the 1100 record and has been used on a transaction. You cannot delete the 1100 record”
I’ve deleted all Not posted journals those main accounts/vendors / Customers and financial dimensions and all account structures, but still the same error.
Until and unless go to the back end tables , end user can not delete those wrongly created master records.
Seems to be MS forgot the some basic concepts .
Just think in a End user point of view , how can user delete the main account / vendor account /Customer account with out going to back end table level as mentioned above ?
The table structure of AX and the inter-related setup means that you cannot delete all records once you have started.
“When you add new records to financial dimension entities (Main account, Department, Cost center, etc.), they are merely available for use and can be immediately deleted. However, as soon as they are actually used, additional records are created in tables such as DimensionAttributeValue, DimensionAttributeValueCombination, DimensionAttributeLabelValue, and many others. Even if you then delete the journal line that referenced the new Main account, the fact that you have ever used it means that these records will exist forever. AX provides no mechanism for deleting these records. The only method would be with direct SQL, and the schema behind those tables is rather complicated.”
At the point you start creating these records you have taken a forward step, you would need to remove the supporting tables NOT from the UI - it is not a simple job and you need to understand all related tables which is why it needs to be done very carefully.
MS have not forgotten basic concepts here, they are enforcing them, not allowing deletion when supporting table entries exist. Whilst I understand this is an issue from your perspective and they could arguably have coded this better you work with what is there, so now you need to remove the supporting entries by code before deleting those records.
When you add new records to financial dimension entities (Main account, Department, Cost center, etc.), they are merely available for use and can be immediately deleted. However, as soon as they are actually used, additional records are created in tables such as DimensionAttributeValue, DimensionAttributeValueCombination, DimensionAttributeLabelValue, and many others. Even if you then delete the journal line (presumably) that referenced the new Main account, the fact that you have ever used it means that these records will exist forever. AX provides no mechanism for deleting these records. The only method would be with direct SQL, and the schema behind those tables is rather complicated.
“Just think of it from the end user point of view” - the answer simply means they cannot do it. The table structure means once created you have gone too far and cannot back out, you need to get people in to remove the entries from the tables.
hi, check your build version. if you want to get rid of this issue, you have to update your build version to this one " #6.2.1000.4051" . for more information read this KB 2885603.
Faiz said it did, I just pasted the link to the KB [:D] That is the KB he says resolved the issue, I did not read it I just did the search work for you because you could not find the link despite him giving you the KB reference. I would suggest you look at the issue search in lifecycle services, it is very simple to use.
I shared it earlier in this post, click on it. The reference is CU7, so Faiz is saying you need to be on CU7 then you will not have the issue. I have not tested this, but you need to. Faiz also said you could contact him by skype in the post, so I suggest you do that if you want any more information from him on this matter.
