I have turned on the control for the editable grid on the Contact entity and am able to use the grouping function, but not edit. All of the fields are locked. I am able to edit fields in the grid in our development site, but not in our production site. I have tried this on the Account and Opportunity entities as well.
Attached is a screen print of what the row looks like in production with all the fields locked. We are on CRM 2016 on premise.
*This post is locked for comments
Toni's Answer is verified answer.
Hello Toni,
Thank you so much for the quick response, that resolved the issue.
Thank you
Sandeep
• If the organization is Production, please proceed with a backup first
• Run the following query on the MSCRM_CONFIG DB
SELECT IntColumn
FROM DeploymentProperties
WHERE ColumnName = 'metadataquerymaxdepthofnestedfilters'
• Validate the value for that field is not an integer
• If it is any value either than “25”, please proceed to the step below:
UPDATE DeploymentProperties
SET IntColumn = 25
WHERE ColumnName = 'metadataquerymaxdepthofnestedfilters'
• Do an IIS reset and test it again
Toni,
Can you please share more information on what had to be changed in the WebAPI configuration? Was something changed in IIS?
Mark, after months of working with Microsoft on this to no avail, we finally have resolution. In working with a third-party vendor solution, we encountered an unrelated problem to which the solution was to configure our web API properly. When we did this, we noticed our grids suddenly became editable. So the answer for us was in the web API. Hope this is helpful!
Mark, this is our version builds right now:
• Production: SQL Server 2014 SP2 CU4 (build 12.0.5540.0) -- Editable grids are not working
• Development: SQL Server 2014 SP2 CU4 (build 12.0.5540.0) -- Editable grids are working
Thanks, Aric. Yes, I am the SysAdmin. We have tried disabling our javascript that locks certain fields OnLoad, but all fields were still locked. All fields on all records in all entities are locked all the time. =(
Toni,
Thank you for sharing your latest attempts to resolve this annoying issue. We have not yet opened a case with Microsoft, but we intend to if we cannot find a resolution ourselves in the next day or two.
Do you happen to know what the different SQL patch levels were for your two environments, prior to your most recent updates?
In our case, we are using the following:
I am curious to know what patch levels you are using in your respective environments.
I am not certain this is the cause, only speculation at this point. So far, though, this is the only difference I have identified between our two environments. I may attempt to rollback the CU3 update, if I am able, to see if this changes the results in development. If and when I do, I will be sure to update this thread.
Thanks,
Mark
Mark,
We have been working with Microsoft for a couple of months now with no resolution. We checked our SQL Server patch levels, and sure enough, they were different. We updated to make them the same and re-tested. Same issues. Let me know if you find resolution as we would really like to use this feature. Thanks for reaching out.
I would think there is a possibility of separate business unit security, which is why they would be locked, but you are mentioning that you see this as SysAdmin?
In Dynamics 365, you can use the same JavaScript code to lock records on the form as well as on the editable grid. Is it possible that the logic that is locking your fields on the form is also locking them on the grid.
Also, if you open one of the records on the grid (double click to open on the form), does the form state that the record is Read Only or Disabled.
Just a few pointers that might help guide you in the right direction. Hopefully...
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,240 Super User 2024 Season 2
Martin Dráb 230,149 Most Valuable Professional
nmaenpaa 101,156