You’re offline. This is a read only version of the page.
I have a DIXF entity for a standard table and it's updating records instead of inserting them. The entity is for CustTrans. So I checked the relations and they are there on my entity. Then indexes on both system table and the entity. There are no indexes that were generated for the entity table.... and I think it's because CustTrans does not have a unique index. It uses the recId as the primary index. In this situation is it possible to even use DIXF to import records or how do I get it to insert records vs just updating them.
*This post is locked for comments
We're getting off track... I'm not aware which system is your old system. If you provide an invoice number in the invoice field, AX treats it as an invoice. If this field is empty it is another transaction which could be a payment settlement.
The problem is when I do a General Journal in the Transaction form it comes in as a Transaction type of general journal when it is wanted to appear as the type it was in the older system. So as a Sales order or a payment.
Hi Dougq,
Yes. Like said above, this entity is used to fill a journal. You an then check the details before posting. Note that it will post ledger transactions as well. Usually I use an offset account called "opening balances" which will be reversed during posting the joirnal with the complete opening balance. This account is then used in stead of the customer and vendor main accounts.
Andre, Thanks for the help. I've managed to avoid using DIXF for import into CustTrans/VendTrans and believe to have found an alternative. I'm curious about using the opening balance entity. Would that be a valid way to transfer all needed data from the CustTrans/VendTrans tables on an older (2009) ax system to 2012 so that they would show up in the customer transaction history correctly as sales orders/payments/etc?
The wizard for creating entities is creating base objects. Not always correct. You have to verify the outcome after using the wizard. Please let me know if updating the relation by removing the duplicates will help.
You can read on my latest blog about the effect of this relation from the staging to the target. kaya-consulting.com/microsoft-dynamics-ax-blog
Currently what's related is Voucher, TransDate, AccountNum (for some reason it put it 2x) TransDate, and voucher again. I'm not sure if these duplicates are impacting it but I will remove them. again this was the generated entity.
and I agree with your assessment on not inserting records into custtrans directly.
Hi Dougq,
First of all it is not recommended to insert transaction in the custtrans table directly. You can use the Opening balances entity to upload customer transactions and then post them.
Technically: Check the Relation from the staging table to the CustTrans table. Is there any relation defined and on what fields? The fields in the relation should define the uniqueness. The primary or replacement key of a target table is a fallback, but as you said the CustTrans table does only have the RecId as unique index.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,113
Super User 2024 Season 2
#2
Martin Dráb
229,918
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (