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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

Sharing attributes between entities

(0) ShareShare
ReportReport
Posted on by 385

Is there a way to share an attribute between two or more entities?  Our implementation uses several custom entities to manage different facets of the sales process.  Some of the attributes on these entities are shared.  Is it possible to create an attribute on one entity and view / change that attribute from other entities?

 Thanks in advance for your help!

*This post is locked for comments

I have the same question (0)
  • santosh kore Profile Picture
    75 on at

     I guess its possible if you have a relationship between entities.

  • Mitch Milam Profile Picture
    on at

    There is no way to accomplish what you described.  As Santosh mentioned, you can create relationships between entities that will allow you to put that "link" on a form, but there is no way to create an attribute on Account then add that attribute to the Contact form, for instance.

    On a side-note, you can reference fields of related entities on Views.

    Mitch

     

  • dpacker Profile Picture
    385 on at

    Mitch and Santosh - thanks for replying.  I'll keep the entities synched the 'hard' way - through JavaScript and SOAP!

  • Anton Wilson Profile Picture
    5 on at

    You can have some of the same attributes on different entities and pass through the values of these at the time that you create the related record which represents the next step in the Sales Cycle.

     You do this via Atttribute Mapping on the relationship between the two entities, in your customisations.

     What you need to be aware of is the key limitiation to this - that the mapping of these attributes is a one-time only event - i.e. when you create your related record, it copies through the values of mapped fields into the new record, but subsequently, there is no relationship between the fields on the new entity record and the corresponding fields on the old entity record.  The mapping happens only once.

     This ought to be ok in your situation, as if the Sales process has moved on, the the old record will be de-activated and you'll be left with a record in a new entity representing the current stage of the Sales process?

     

    If you do want them to be updating each other past the initial mapping, then as you say, you'll be into .net or javascript / xml territory.  Workflow would help you so far, but not with picklists.

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

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…

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans