I have a client who migrated to MS CRM Online in April, they've reported a number of cases where their data has updated itself, for example:
Custom entity data records disappear and the related record entities then show another record value.
Ownership of accounts/contacts changed. 2500+ accounts changed ownership in a 10 minute window. (Surely this can't be human error). The audit log show one specific user having updated all 2500+ records.
There are no scheduled tasks running other than those configured and managed by Microsoft.
There is only one plugin that automatically creates a SharePoint Doc folder for the activities entity and moves any attachments to the SharePoint Folder.
Any ideas/suggestions would be greatly appreciated.
Could be a couple of causes, those that jump to mind; a user manually bulk editing records or cascading relationship behaviour,
Related
Theoretically I'm sure there is probably no limit, but realistically I'm looking to understand how many users can be added into a MS Dynamics 365 Team. I'd like to understand what impact adding more than 8,000 users to a single team would have in terms of performance of the Dynamics application.
Why so many users in a team? We're looking at a potential requirement, which needs to secure 4 fields on an entity so that users can create those fields but not view the data in them. Short Answer: Field Level Security. However, we have a large user base ie. 8,000 users and once we create a field security profile, we need to assign that profile to 8,000 users. So an idea was to create a Team and assign the field security profile to the team. Then add 8000 users into that team.
So back to my original question. Is this a plausible solution and is there anything we're overlooking in going ahead with this. Would we face performance issues going forward? Is there a better/alternate solution to meet the requirement?
This 8k users + team + FLS scenario should not be a problem, as I remember from this performance benchmark (on online CRM 2016 update 1 though. ie v8.1), the testing was performed and gave better results with below configuration to prove statistically.
Field-level security was also enabled on custom attributes to reflect
a realistic enterprise organization.
Based on customer research, each user of a specific role was assigned
a realistic set of data. The data that the user would own was based on
the user’s role. Before the test, the total data in the test database
included more than 656,549,587 business records with a total database
size of 1.024 TB.
TeamMembership with 61,406 records.
A batch of 17,868 concurrent users performed create, update, and
delete (CRUD) operations within Dynamics CRM Online.
Need help with deleting a user out of 15 different instances of MS CRM Dynamics. Is there a faster way of doing this rather than deleting the person out one instance at a time?
Whether it is crm onpremise or online, deleting systemuser is not possible (atleast by supported way) & not recommended to do in unsupported way (like SQL Delete in onpremise).
You can remove all the security roles & teams she/he is part of (take care of all WF, records they own)
Only you can disable by doing so in onpremise or by revoking license in O365 portal to replicate in crmol
If the AD account is removed/disabled it should replicate in Dynamics
No way to do in bulk across organizations anyway
Edit:
Based on comments, C# Console application can be developed, to iterate through multiple CRM connection strings & issue a sdk Service call to target system user record in each instance.
I'm evaluating CRM 2011 to replace an existing app and and have some questions about security and segregating information by Client (or Account).
I have a custom entity for 'Client'. There are lot of custom entities that are related to 'Client' which consitute the data needed to be captured.
I would like to limit specific teams/users to work on specific clients and see only the data for those clients that they have access to.
I'm seeing that individual entities can be assigned to teams/users but I need all related entities to be locked down by Client so that regular users
Dont see records in views or searches that belong to other clients.
Can't create or access records for other clients.
Can this be done in CRM 2011? How?
Also - is it possible to limit processes/workflows to operate or trigger on records of specific clients only?
Probably the easiest thing to do would be do base your security on business units. Groups of clients an their related records would all be in the same business unit, and as long as you set their security roles to only allow access to records in their own business unit, that would work.
For workflows that only trigger on particular clients, it depends on the exact requirements. You could certainly check the business unit of the client as the first step in the workflow and continue or exit based on that. If it's something more complex, you can write a custom workflow assembly to do the check for you.
Do you know of a way to get rid of CRM User accounts in MSCRM 4.0? After some user accounts have been deleted in AD we're faced a lot of issues while importing the organisation to another server stating that there are issues with the user mapping.
What kind of idea is behind the fact that no user accounts can be deleted from the crm installation? Is there any tool or undocumented Webservice API call to get rid of crm users?
Thanks for sharing yours insights
There is no working way of actually removing CRM users from the database; I think one reason is that it would cause all the records previously owned by a now deleted user having no owner at all (the same goes for the createdby and modifiedby fields), which would put the database in an illegal state.
The official way of removing a user from the CRM system is deactivating the systemuser record. This does not sever the connection to the AD user, however, but I think deactivated users should not cause problems when reimporting the organization; I'm not sure of that, though.
You could theoretically delete the systemuser records from the database using SQL, but that's highly unadvisable.
Changes in the AD users are actually causing various issues with MSCRM quite often; a larger customer even had us develop a solution for automatically synchronizing their CRM users with the state of the AD because managing that manually proved to be too much work in a large environment with a few hundred users.
Is there a way to track user activity in Microsft Dynamics CRM? The end result would be a list of users, showing a datetime for each access into CRM, and possibly what modules are being accessed.
Also, is there a way to tie users to database connections, as is done in AX?
Why do you want to do this? The reason I ask is because there are many different ways to log user access depening on purpose.
Detailed access logging can be performed by IIS (web log).
Logons are also tracked in the Event Log->Security log.
Changes to entities can be tracked by implementing an audit log using workflows (or buying a third party component to do this).
The third option is to write a .NET plugin that logs whatever you want on whatever event you want on the entities you choose. Lookup plugins in the Microsoft CRM SDK for more information on how to do this.