We have a on-prem instance of Microsoft Dynamics CRM. The associated entities in all the forms come up blank and no records show up.
When I get this error in on-prem environments, it's usually because the database is getting pinged and queries to it are timing out. You may want to check the database to see if it is being overwhelmed and unable to return data.
we ended up updating the CRM version to resolve the issue.
temporary fix was implemented by restoring a backup of the database.
Related
after successfully upgrade to dynamics from 2016 8.1 to 9.0.5 on prem,
we encountered a problem with business process flow,
as we know each bpf has its own entity in the DB,
we use an OOB bpf in incident entity that called phonetocaseprocess,
the problem is that i saw after the upgrade that the newly table created for
that bpf - is empty :() , so all the current incidents failed on update because
i get an error that said that : phonetocaseprocess With Id = 196dc1e2-466f-e911-80e6-
00155dc4022d Does Not Exist.
when i create a new incident record it works fine and a record is created in
phonetocaseproccess table.
someone encountered that? or have an idea? thank you
UPDATE
we were able to resolve this by running the script provided in the above forum before the upgrade run, after this the upgrade was successfully completed.
https://community.dynamics.com/crm/f/microsoft-dynamics-crm-forum/232669/business-process-flow-instance-exists-error-after-crm-2016-upgrade/639024
The problem occurred because processes in the source environment did not have a unique name in the database, which resulted in the upgrade not converting the data to the correct table in the DB but to another table in new_bpf_guid format.
hope this will help someone
That's because your existing records are related to the older process and that the process in the newer version has different GUID. See the snapshot below:
To correct this, you have to migrate the process entity data with the existing primary keys in the older version.
I am using scribe to migrate the Principal Object access data from CRM 4.0 to CRM 2016 DB.
The source adapter is a SQL Data Adapter which reads the data from the POA table in 4.0.
The destination adapter is the CRM Adapter and I have an insert step to insert the data into CRM 2016.
In the destination adapter, Scribe does not allow me to add the data links to PrincipalId and ObjectId fields from the source.
As far as I know, both of these fields are required to create a principal access object. However, since I can not create the data links, I do not know how I can copy this data over to CRM 2016.
Has anyone ever tried to Migrate the Principal Object Access table using scribe and have any suggestions for me to try out?
Any help will be greatly appreciated.
A few things I've noticed from your screenshot that might help you out:
You're trying to set the principalobjectaccessid on insert. I would think this is a no-no as you are creating a crm record and want a new guid to be assigned at that time instead.
You're doing the lookup to the type code but not to the foreign keys for the objectid and the principal id. You would need to refer to those (probably by name or an xref table as the guids will be different post import) in order to get the sharing in place.
In order to lookup those objects and principals you will need them to be entered into CRM2016 in a prior step.
One caveat I'd add is that based on the limited knowledge I have of you trying to move a 4.0 thought process involving sharing over to CRM 2016 this very well could be a bad idea. While sharing is still supported and certainly a part of the application there's performance issues that come up with extensive sharing and it's honestly a much more complex thing to work with then utilizing teams.. As I'm sure you're noticing now.
The POA table is internal to CRM and shouldn't be written to directly, even via the API.
It stores details of how records (determined by the objectid) are shared to users/teams (determined by principalid).
It sounds like you want to migrate your shares from CRM 4.0 to 2016. Scribe has a mechanism for doing this, using virtual fields. Look in the help for "Adapter for Microsoft Dynamics CRM" and search for "Granting Access". This explains how to use the virtual fields.
Can you migrate system users prepared in staging database to CRM 2013 Online using SCRIBE?
I need to create 750 users (currently in CRM4) in CRM online and assign them to their source BUs. (Root BU excepted). I can stage them as required.
Can I migrate these users?
You cannot create users to a CRM Online using Scribe, you can only update them.
I have this issue recently and my solution was:
Create a DTS to create an CSV file* with the users: You can add the users using the Office portal or through the PowerSehll.
Creates a DTS with all the other information about the users (The CSV is pretty basic, so you will need to add all the other information related to every user).
Create a DTS with the relation between Users and Roles
*You can see the csv format in your Office portal, under Users->Active Users->Bulk add
https://portal.office.com/default.aspx##/UserManagement/ImportFile.aspx?refer=%2FEAdmin%2FUser%2FActiveUsers16.aspx
Maybe there is a quicker way to do it, but this was the approach I found.
Note that Scribe Insight isn't able to change a users business unit.
When I had a similar requirement (to update the business units of a large number of users) I uses SQL Server Integration Services.
Mike
I am attempting to import a large database into Dynamics 2013, which has a lot of activities against Accounts and Contacts. When I import the Phone Calls/Emails etc. they all appear in the Activity feed labeled as today. I have Over-ridden the Created on date, but the feed is ordered by the modified on column.
If this was for on premises I'd just go into the database and run an SQL query, but since this is destined for Online that's not an option, I have tried creating a plugin but that seems to ignore/over-ride the change.
Has anyone got any inspired ways of over-riding the modified on date?
You cannot set the value of ModifiedOn in a Online organization. There is no CRM SDK call that will allow the setting of the ModifiedOn date of a record. Therefore without SQL access, as you state in your question, this value cannot be changed.
you can update modified on through a pre-update plugin in CRM online or on-prem. This is the only supported solution.
You may also modify SQL directly.
http://missdynamicscrm.blogspot.co.uk/2014/06/crm-2011-2013-modify-createdon-createdby-modifiedon-modifiedby-using-SDK-CSharp.html
We have restored an old ms CRM database over a newer version. But when I try and add users which were already existed in newer version I get an error.
If I delete the users from our of active directory and then try to add them to CRM it works fine.
Is it possible that CRM is storing user information in the MSCRM_CONFIG. And can this be removed in a supported way?
Have a look at the SystemUser in the MSCRM_CONFIG table, I think i need to remove the users from this table. but I can't do a delete statement as it's not supported. :)
Did you restore this database using the Deployment Manager tool or simply by doing a SQL Restore? Doing this directly from SQL would cause issues. You'll need to delete the organization in the deployment manager and then delete the database in SQL. Then you should attach the database and recreate the organization from the deployment manager, pointing it to the existing database.
Restoring just the org DB can lead to issues as some user info is stored in the config DB as well. In fact, there are entries in there mapping the user to the org (SystemUserOrganizations), so when you restore the Org DB, this mapping is now out of date.
You would need to either go the Delete/Import route or manually do some unsupported cleansing of the Config DB Tables.