web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Season of Giving Solutions is Here!
News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / get data from data entity
Finance | Project Operations, Human Resources, ...
Suggested Answer

get data from data entity

(0) ShareShare
ReportReport
Posted on by CU22120935-0 44
Hi,

If I have an entity, and i want to get a field value from another table for export purposes

Would it be better to join to that table with Read only and add this field alone OR create a computed column to return the value of that field? is the performance the same?
I know computed column is more complex but what is better?
Categories:
Dynamics 365 Finance
I have the same question (0)
  • Suggested answer
    André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 301,496 Super User 2025 Season 2 on at
    Hi,

    You can create virtual fields in two ways: 
    1.  X++ method and call postLoad() to fill the field values
    2.  T-SQL > X++ method for extending the SQL query
     
    If you are using the second option, or join a table, there is no difference in performance as all will be executed on SQL server. If you use the first option, then there will be a performance penalty.
  • CU22120935-0 Profile Picture
    CU22120935-0 44 on at
    Hi Andre,

    Yes my question was about computed columns (T-SQL) vs joins (not virtual field with postLoad)

    so if it's the same performance, i'm free to use whatever.
  • CU22120935-0 Profile Picture
    CU22120935-0 44 on at
    @André Arnaud de Calavon

    To add to my last reply. If i leave allow edit for the computed field as Auto or make it No, it would still be the same right?
    We can't edit computed columns anyways?
  • Martin Dráb Profile Picture
    Martin Dráb 238,175 Most Valuable Professional on at
    I would prefer a join - it's less work and you can easily use multiple tables from the joined table.
    You can allow import to entity fields backed by computed columns. The value won't be stored anywhere, but you can write to do so.
  • CU22120935-0 Profile Picture
    CU22120935-0 44 on at
    Hi Martin,

    I'm afraid i didn't understand this "You can allow import to entity fields backed by computed columns"
    Can you please explain with an example?
     
    And does it then matter if I make it allow Edit No or Auto?

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.

Helpful resources

News and Announcements

Season of Giving Solutions is Here!

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Abhilash Warrier Profile Picture

Abhilash Warrier 763 Super User 2025 Season 2

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 413 Super User 2025 Season 2

#3
Martin Dráb Profile Picture

Martin Dráb 284 Most Valuable Professional

Last 30 days Overall leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans