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

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / Adding new field to en...
Microsoft Dynamics CRM (Archived)

Adding new field to entity, then to view, will not show data

(0) ShareShare
ReportReport
Posted on by jfine 19

So I added a new field to an existing entity, let's call the field SpecialName, entity name = Application. It's just a single line of text field.

Checked the view in sql server, and saw that the field was there, in the view and the base table, Perfect so far.

Now I want to bring back data, so for a test, I manually altered the view in sql server, by changing myBaseTableName.SpecialName to 'test' SpecialName.

Manually ran the view in sql server and sure enough, every single row had the word 'test' in that column. Still perfect.

Added this new field to a new view using CRM. A copy of an associated view that only had 2 fields. So now my new view has 3 fields total, published.

Tried using the new view in CRM, and the 2 existing fields return data as expected, just like the view it was copied from, and the new field name (column) is there, but, no data.

Refreshed, republished, etc., you name it, still no data.

Why?

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Temmy Wahyu Raharjo Profile Picture
    Temmy Wahyu Raharjo 2,916 on at

    What do you mean with altered the sql? Don't change directly from SQL. If you want to custom the view, use the official way. If your table got relationship, you can directly refer to the attribute easily.

  • jfine Profile Picture
    jfine 19 on at

    "What do you mean with altered the sql?"

    I mean I altered the view, changed the SQL, etc., "by changing myBaseTableName.SpecialName to 'test' SpecialName." If I run the view manually, it works fine. All this is doing is replacing a column in the view with static data, and keeping the column name the same.

    This should work. And I'm looking for the reason why it does not. Sure I can beat on the view using the official way, but this column need to be a special case statement eventually, but in any case, adding static data to the view directly using SQL server should not change the way the CRM view retrieves data since the column name is the same. Makes 0 sense.

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…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

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