I've seen a few similar posts, but none with a solution. After importing / upgrading an Organization into D365, the status is failed. The most common error in the log is "Entity incidentresolution : Quick create is not supported for non-refreshed Entity".
Will someone please help me resolve the error?
I received the following solution from Microsoft Support, which I am posting here for future reference.
You will need to attach a non failed database again to the SQL server(fresh one) apply the following script before attempting to import, once you ran the script, please retry the import.
Script:
BEGIN TRANSACTION
IF NOT EXISTS (SELECT * FROM sys.objects
WHERE object_id = OBJECT_ID(N'[dbo].[IncidentResolutionBase]') AND type in (N'U'))
BEGIN
/****** Create the metadataschema to add support for the Extension Table required for the incident resolution custom attributes******/
CREATE TABLE [dbo].[IncidentResolutionBase](
[ActivityId] [uniqueidentifier] NOT NULL,
CONSTRAINT [PK_IncidentResolutionBase] PRIMARY KEY CLUSTERED
(
[ActivityId] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, FILLFACTOR = 80) ON [PRIMARY]
) ON [PRIMARY]
ALTER TABLE [dbo].[IncidentResolutionBase] SET (LOCK_ESCALATION = DISABLE)
ALTER TABLE [dbo].[IncidentResolutionBase] WITH CHECK ADD CONSTRAINT [FK_IncidentResolutionBase_ActivityPointerBase] FOREIGN KEY([ActivityId])
REFERENCES [dbo].[ActivityPointerBase] ([ActivityId])
ALTER TABLE [dbo].[IncidentResolutionBase] CHECK CONSTRAINT [FK_IncidentResolutionBase_ActivityPointerBase]
END
/****** updating the metadataschema to add support for the Extension Table and Required metada data attributes on incident resolution entity******/
UPDATE mse
SET IsReadOnlyInMobileClient = 0, IsQuickCreateEnabled = 1, CanCreateAttributes = 1, IsAIRUpdated = 1, ExtensionTableName = 'IncidentResolutionBase'
FROM [MetadataSchema].[Entity] AS mse INNER JOIN [SolutionBase] as sb on mse.SolutionId = sb.SolutionId
WHERE mse.LogicalName = 'incidentresolution' AND sb.UniqueName NOT IN ('msdynce_ServicePatch201911', 'msdynce_ServicePatch', 'msdynce_Service');
DECLARE @updatedRows AS INT = @@ROWCOUNT;
DECLARE @solutionCount AS INT = (SELECT COUNT(UniqueName) FROM [MetadataSchema].[Entity] AS mse INNER JOIN [SolutionBase] as sb on mse.SolutionId = sb.SolutionId
WHERE mse.LogicalName = 'incidentresolution' AND sb.UniqueName NOT IN ('msdynce_ServicePatch201911', 'msdynce_ServicePatch', 'msdynce_Service'));
IF @updatedRows <> @solutionCount
BEGIN
THROW 51000, 'Incorrect rows updated!', 1;
END
COMMIT TRANSACTION
Raise a ticket with Microsoft, This looks to be a System error.
Hi Justin R,
This seems that this is a system error. You would better raise a ticket to feedback this.
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,253 Super User 2024 Season 2
Martin Dráb 230,188 Most Valuable Professional
nmaenpaa 101,156