Advanced Customization Wizard Entity -- Regular user cannot see entity tab

Help please! I have created a secondary entities with the Advanced Customization Wizard and the only users that can see the tab for the newly created secondary entity are System Admins. I am not sure where I went wrong. The entity is secondary to the company record. When viewing the data, the user would be in the context of the company. Everything works great for System Admin users. However, I am puzzled as to why users without System Admin rights cannot see the tab when on the company record.

I did not place any user or team specific data in the SQL where clause of the secondary entity tab for the company. However, there is a field on the company table that indicates whether or not to display the tab. The field is comp_sapphiretab. Therefore, I have this in the SQL where clause for the tab comp_sapphiretab = 'Y'.

I have a very basic asp page that displays the data and I don't believe I have any user or team restrictions in the asp page. In the ASP page I am using

CRM.GetContextInfo to get the companyID and CRM.FindRecord (linked to the company record) to get the data for the tab.

I have looked at Territories and Security Profiles. However, they seem to be related to main entities rather than secondary entities. I am not sure where I need to look to determine why only system admins can see the new secondary entities tab.

Any assistance that could be provided would be greatly appreciated. Thank you! I am using CRM 2017.

  • 0

    hi Michele - Have you checked the field level security on the comp_sapphiretab field?

    paul

  • 0

    Michele

    You may be treating the new entities as secondary entities BUT all new entities created by the Advanced Customization Wizard are created as Primary Entities. This means that they are covered by the security profiles. Your users must have the rights to View the entity at the minimum.

  • 0

    Thanks Paul. Yes. No field level security on the field.

  • 0

    OK. Good to know. Thanks! I had changed them to secondary entities in Advanced Customization --> Tables and Database. Therefore, I have changed them back to primary entities and applied the security profile permissions. After applying the permissions, I changed them back to secondary entities.

    Other than the security profile, is there any harm in me changing an entity created with the Advanced Customization wizard as a secondary entity? I am aware that I have to modify the asp pages that are created to attach it to the entity in context.

    Your assistance is greatly appreciated...Thank you!!!

  • 0

    Jeff: I discovered that if I change the entity to a secondary entity, the users still cannot see the tab even though I gave them the Security Profile permissions. Bummer. Therefore, even though I am using it as a secondary entity, it appears that I am going to need to leave it as a primary entity in the system.

    I have learned a lesson that if I really want it to be a secondary entity, I should not use the advanced customization wizard. However, the wizard is nice because it sets up a lot of the necessities for you...even when you want a secondary entity. Even though I had to modify the asp pages....everything else it provides is great! (Except for the fact that non system admins cannot see the entity... :-)

    Is there a component to create a secondary entity? Not having to create the "basic" table fields is a time saver (createdby; createddate, updatedby; updateddate; timestamp ) those are five fields that CRM.CreateRecord will populate for you (even on custom entity not created with the Advanced Customization Wizard..I think?). In addition any id fields you need are created along with your custom pages folder. Not having to remember to do all that is great when customizing the system.

    Anyway...thank you...thank you...thank you! At least know I understand the error of my ways!! :-)

  • 0

    hi Michele

    Those fields are created for you when a new table is created in Administration/Advanced Customisation/Tables and Databases. If you fill in the column name fields for Description, Company Id, Person Id, User Id and Workflow Id then those fields are all created too.

    Leave 'Top Leveel Entity' set to 'No' to create a secondary entity.

    paul