Announcements
No record found.
Hi,
I have duplicated the GeneralJournalAccountEntryEntity . I had a requirement to add the unmapped non-computational field. It takes a lot of time to export the data. Any better way to get the data in quick manner?
Hi Harshal, Virtual fields are executed row by row therefore cause slow performance. Check if you can create computed column instead of Virtual field.
HI Mohit,
Thanks for the solution. I am trying to get the account name for the particular account in entity. I saw the existing computed column but could not understand it. Can you please provide the solution to get the accoun or the link where i can see the information related to SystemComputedColumn?
Can you add that via entity datasource? You need that for export. Then this way will not impact performance.
Hi Preetham,
You mean to sat mapDatasourceToEntity method? If yes then can you please give any enity example where I can look into?
I don't mean you to write the code. If you go with code, it will anyway impact performance. As you require the name of the account number, let's assume you have to do same in form level. So, what you do? You will add that datasource in form, give the relation and set the join property. Finally, you will get the name of the account. Similarly, you can do the same in the entity as well. That won't impact anything.
Hey Preetham,
At form level they have written a display method with if and else condition, thats why I am trying to write a code. Also I need the financial dimensions seperately. For that also I would be needing the code to write.
For performance the way I said is good. Can you try that display method as I said?
If not possible then you have to do that in postload method.
I had written the display method logic in postLoad and it gave me the performance Issue. That's why I am asking how I can write in Computed column or mapDataSourceToEntity.
For computed column you can try this link.
www.atomicax.com/.../part-16-action-methods-and-computed-columns
As I said earlier you can only write postload for export and not mapentitytodatasource as the 2nd method is for import.
You can check mapDataSourceToEntity method from below article and get table buffer by finding GeneralJournalAccountEntryRecId in table's RecId. However, I don't think it will improve performance but you can try. Creating Computed method is tricky due to various conditions and method calls in display method. Another solution is to create custom table to store that accountName and use that table as dataSource in the entity. So, it will be mapped field instead of Virtual field. You have to write code in insert & update of MainAccount and MainAccountTranslation table, so if value is inserted or changed it should be updated in your custom table as well.
nareshdax.blogspot.com/.../entity-methods-in-ax7.html
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Congratulations to our 2026 Super Stars!
We are thrilled to have these Champions in our Community!
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Giorgio Bonacorsi 689
André Arnaud de Cal... 478 Super User 2026 Season 1
Syed Haris Shah 258 Super User 2026 Season 1
