I'm working with MS CRM 2015. Some of my Organization data base having multiple records in the Organization Table. Looks like whenever I do database backup and restore and then org import, it is creating additional entries in Organization table, but not deleting or disabling the old entry. Sometimes this record count increases more when we do multiple backup-restore-imports. Not sure how CRM handles this.
Now one of the Organization import not working. Org import dint give any error, but when we try to access the CRM UI, it throws error as "The user ID associated with the current record is not valid". But user is available in the Source organization and source and target organizations both in the same domain etc. Looks like multiple times of Org import messed up some CRM config data. Anybody have any idea?
Error from Event log is,
Exception information:
Exception type: CrmException
Exception message: The user Id is invalid. at Microsoft.Crm.BusinessEntities.SecurityLibrary.GetPrivilegedUserCallerAndBusinessGuidsFromThread(WindowsIdentity
identity, IOrganizationContext context) at
Microsoft.Crm.BusinessEntities.SecurityLibrary.GetCallerAndBusinessGuidsFromThread(WindowsIdentity
identity, Guid organizationId, LocatorServiceContext
locatorServiceContext)
Related
We have used the case Entity, there is default user that is used to assign a case on new creation or reactivation.
We have a workflow created for Case Reactivation, so whenever a case is reopen it is assigned to the default system user. It was working fine till September 20, but now when you give the survey after case resolution and then try to reactivate it it throws error in workflow. It works fine when you try to reactivate without giving the survey.
Error:
The real-time workflow named "Case is Resolved/Reopened" failed with the error "Principal user (Id, type=8, roleCount=1, privilegeCount=619, accessMode=0), is missing prvReadmsfp_questionresponse privilege (Id) on OTC=10247 for entity 'msfp_questionresponse'.
The System user has the role assigned as of salesperson, giving permission for this entity to salesperson does solve the issue, but the salesperson role is being used by many others to whom permission for this entity can't be given.
Can anyone tell us why this started causing issue after a particular time. Was there any updates from Microsoft Forms Pro for this entity?
Its very possible there have been updates from MS. You can review the solution history in make.powerplatorm.
https://learn.microsoft.com/en-us/powerapps/maker/common-data-service/solution-history
Look for the forms pro solution and check the solution history.
Is the "Default" user an actual person that logs in? Or a Service account that is only used for automation/workflows?
In any case, I'd suggest creating an add-on or feature role called something like "Question Response Reader" that only has the read permission for that entity. You can then add that role to the default user, and any other users that need to read that entity.
Probably Microsoft changed something in the background especially w.r.t security of forms Response entity msfp_questionresponse.
You easily solution is to give proper security rights to user who is ruining your workflow.
If it is run by the owner of the workflow then that user, if workflow runs under the context of user then that user should have read rights for entity msfp_questionresponse
The Account Entity has an OOB field called Address Type and default values are Bill To, Ship To, Primary and Others. By mistake, we deleted the values Bill To and Ship To from the Default solution. From then onwards we are not able to open the form containing the Address Type field unable to open the Field again to re-add the values and also unable to add any new business rules or modify existing business rule for the Account Entity.
Please note: From the Account form if I remove the Address Type field, then my form is opening without any errors.
When creating a case I get the below error.
Access Error The system could not log you on. This could be because
your user record or the business unit you belong to has been disabled
in Microsoft Dynamics 365. If you contact support, please provide the
technical details.
This occurred shortly after deleting the CRM Admin user and creating a new CRM Admin user in the Office 365 users screen.
The more technical message is
The user with
SystemUserId=bb51ba1c-66e8-4dc1-82ca-cb64e25f3ff9 in
OrganizationContext=7e061672-3a31-4588-9770-9f94711c7f09 is
disabledDetail.
The error message is saying that the user with that ID is disabled so the first thing to do would be to open that record and check which user it is.
To do that, use the URL below but replace the xx's and the yourregion part of the url (I've already added your user id).
https://xxxxxxxx.yourregion.dynamics.com/main.aspx?etc=8&extraqs=&histKey=952109180&id={bb51ba1c-66e8-4dc1-82ca-cb64e25f3ff9}&newWindow=true&pagetype=entityrecord
You will then need to enable that user or resolve problems from there.
I would also check that you don't have any plugins or workflows which have been setup to run as that user when creating a case.
As I understand, we can access records created by Portal users and their respective Entity Permissions apply for them. However, I wanted those users to be able to even access records which were created by CRM users within Dynamics 365 (and not records created from Portal by a Portal user which is assigned to System)
Is this possible? If yes, how can I achieve that?
Thanks in advance!
It does not matter who created the record, what matters is if that user has access to it. It would not make much sense to show only records that were created by the portal users - how would you then handle something like Customer Service (on one end users use portal, but on the other they are using CRM, bot are creating records).
So basically I'm not sure how aware are you of the configuration of permissions, but let's say that you configured that a Contact (which is a portal user) has access to all records "Cases" that are referencing this contact (this is simply configuration in Entity Permission record). If yes then contact will see records created by him and all other cases that are referencing him as a contact, so if you as a CRM user will create a Case for a Contact, this Contact will see the case.
We're using Microsoft Dynamics CRM 2016 on-premise. Is there a way to do a database query on the default form that users will see for a specific entity?
The reason I ask, we have a user that has an error when opening an email form:
systemform With Id = a7415a93-0113-4d90-80cd-280e28dfb4f7 Does Not Exist
This might have been an old form that has long been deleted from our system, and I'm wondering if there are any other users that might have this default systemform ID, as it will prevent them from opening that entity.
Users' most recently viewed forms are stored in the UserEntityUISettingsBase table. You can query the UserEntityUISettings view to see if any users are having the given form as their default form:
SELECT * FROM UserEntityUISettings
WHERE LastViewedFormXml LIKE '%a7415a93-0113-4d90-80cd-280e28dfb4f7%'
Keep in mind that it is entirely unsupported to update the database directly, so I would strongly recommend that you only stick to querying. If you find any forms this way, you should change them in a supported manner.