This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Compliance Kit - Unique Object Enforcement - Changing Built-In Error Message

Dear All,

We are implementing the Unique Object Enforcement feature on our customer's vault and we have 2 questions :

  1. Is it possible to change the built-in error message ? We saw a "Custom Error Message" parameter but it only affects a certain part of the error message displayed, the built-in part stays.
    On the error message detailed logs we can clearly see which line is called in the event handlers (AfterCheckInChanges::MFiles.ComplianceKit.MFEventHandlerAfterCheckInChanges, 22) but there's no way to see where exactly the error message is prompted.
  2. Is it possible to put Placeholders in the Custom Error Message section ?

<MetadataEditor>, -, Script execution failed. ((AfterCheckInChanges::MFiles.ComplianceKit.MFEventHandlerAfterCheckInChanges: 1817299-8)) (0x800408BB)
ScriptErrorHelper.cpp, 96, Script execution failed. ((AfterCheckInChanges::MFiles.ComplianceKit.MFEventHandlerAfterCheckInChanges: 1817299-8)) (0x800408BB)
MDispatchExImpl.h, 688, Script execution failed. ((AfterCheckInChanges::MFiles.ComplianceKit.MFEventHandlerAfterCheckInChanges: 1817299-8)) (0x800408BB)
MDispatchExImpl.h, 850, Script execution failed. ((AfterCheckInChanges::MFiles.ComplianceKit.MFEventHandlerAfterCheckInChanges: 1817299-8)) (0x800408BB)
MetadataCardAction.cpp, 386, Script execution failed. ((AfterCheckInChanges::MFiles.ComplianceKit.MFEventHandlerAfterCheckInChanges: 1817299-8)) (0x800408BB)
MetadataCardAction.cpp, 570, Script execution failed. ((AfterCheckInChanges::MFiles.ComplianceKit.MFEventHandlerAfterCheckInChanges: 1817299-8)) (0x800408BB)
MetadataEditor.cpp, 2959, Script execution failed. ((AfterCheckInChanges::MFiles.ComplianceKit.MFEventHandlerAfterCheckInChanges: 1817299-8)) (0x800408BB)
MetadataModel.cpp, 4269, Script execution failed. ((AfterCheckInChanges::MFiles.ComplianceKit.MFEventHandlerAfterCheckInChanges: 1817299-8)) (0x800408BB)
MetadataModel.cpp, 4706, Script execution failed. ((AfterCheckInChanges::MFiles.ComplianceKit.MFEventHandlerAfterCheckInChanges: 1817299-8)) (0x800408BB)
ElectronicSignatureUIHelper.cpp, 239, Script execution failed. ((AfterCheckInChanges::MFiles.ComplianceKit.MFEventHandlerAfterCheckInChanges: 1817299-8)) (0x800408BB)
MetadataModel.cpp, 12199, Script execution failed. ((AfterCheckInChanges::MFiles.ComplianceKit.MFEventHandlerAfterCheckInChanges: 1817299-8)) (0x800408BB)
CoVaultMountingDocumentOperations.cpp, 3274, Script execution failed. ((AfterCheckInChanges::MFiles.ComplianceKit.MFEventHandlerAfterCheckInChanges: 1817299-8)) (0x800408BB)
DocumentCache.cpp, 11635, Script execution failed. ((AfterCheckInChanges::MFiles.ComplianceKit.MFEventHandlerAfterCheckInChanges: 1817299-8)) (0x800408BB)
DocumentCache.cpp, 11744, Script execution failed. ((AfterCheckInChanges::MFiles.ComplianceKit.MFEventHandlerAfterCheckInChanges: 1817299-8)) (0x800408BB)
DocumentCache.cpp, 20192, Script execution failed. ((AfterCheckInChanges::MFiles.ComplianceKit.MFEventHandlerAfterCheckInChanges: 1817299-8)) (0x800408BB)
RPCMethodCallWithRetry.h, 35, Script execution failed. ((AfterCheckInChanges::MFiles.ComplianceKit.MFEventHandlerAfterCheckInChanges: 1817299-8)) (0x800408BB)
RPCMethodCallWithRetry.h, 35, Script execution failed. ((AfterCheckInChanges::MFiles.ComplianceKit.MFEventHandlerAfterCheckInChanges: 1817299-8)) (0x800408BB)
RPCDocumentOperations.cpp, 12891, Script execution failed. ((AfterCheckInChanges::MFiles.ComplianceKit.MFEventHandlerAfterCheckInChanges: 1817299-8)) (0x800408BB)
RPCDocumentOperations.cpp, 7389, Script execution failed. ((AfterCheckInChanges::MFiles.ComplianceKit.MFEventHandlerAfterCheckInChanges: 1817299-8)) (0x800408BB)
MCallInLoop.h, 712, Script execution failed. ((AfterCheckInChanges::MFiles.ComplianceKit.MFEventHandlerAfterCheckInChanges: 1817299-8)) (0x800408BB)
RPCDocumentOperationsHelper.cpp, 4192, Script execution failed. ((AfterCheckInChanges::MFiles.ComplianceKit.MFEventHandlerAfterCheckInChanges: 1817299-8)) (0x800408BB)
RPCDocumentOperationsHelper.cpp, 3753, Script execution failed. ((AfterCheckInChanges::MFiles.ComplianceKit.MFEventHandlerAfterCheckInChanges: 1817299-8)) (0x800408BB)
RPCDocumentOperationsHelper.cpp, 9432, Script execution failed. ((AfterCheckInChanges::MFiles.ComplianceKit.MFEventHandlerAfterCheckInChanges: 1817299-8)) (0x800408BB)
RPCDocumentOperationsHelper.cpp, 10426, Script execution failed. ((AfterCheckInChanges::MFiles.ComplianceKit.MFEventHandlerAfterCheckInChanges: 1817299-8)) (0x800408BB)
VaultDBSessionEvents.cpp, 380, Script execution failed. ((AfterCheckInChanges::MFiles.ComplianceKit.MFEventHandlerAfterCheckInChanges: 1817299-8)) (0x800408BB)
VaultDBSessionEvents.cpp, 1690, Script execution failed. ((AfterCheckInChanges::MFiles.ComplianceKit.MFEventHandlerAfterCheckInChanges: 1817299-8)) (0x800408BB)
VaultScriptSessionTemplates.cpp, 275, Script execution failed. ((AfterCheckInChanges::MFiles.ComplianceKit.MFEventHandlerAfterCheckInChanges: 1817299-8)) (0x800408BB)
VaultScriptSessionTemplates.cpp, 340, Script execution failed. ((AfterCheckInChanges::MFiles.ComplianceKit.MFEventHandlerAfterCheckInChanges: 1817299-8)) (0x800408BB)
VaultScriptSessionTemplates.cpp, 340, Test evok --> 2 PV LES MÊMES

The object "PV - N°35 - 29/04/2022 - 6 21 018 - Belmont-sur-Lausanne - Chemin des Ecaravez - Autres noms : 62101" cannot be saved. At least one object with the same metadata already exists.
Duplicate object: "PV - N°35 - 29/04/2022 - 6 21 018 - Belmont-sur-Lausanne - Chemin des Ecaravez - Autres noms : 62101" (Document, ID 1816899)

Unique Object Rule: PV Chantier
Description: Check if a mentioned PV already exists (0x80131500)
VaultScriptSessionTemplates.cpp, 523, Test evok --> 2 PV LES MÊMES

The object "PV - N°35 - 29/04/2022 - 6 21 018 - Belmont-sur-Lausanne - Chemin des Ecaravez - Autres noms : 62101" cannot be saved. At least one object with the same metadata already exists.
Duplicate object: "PV - N°35 - 29/04/2022 - 6 21 018 - Belmont-sur-Lausanne - Chemin des Ecaravez - Autres noms : 62101" (Document, ID 1816899)

Unique Object Rule: PV Chantier
Description: Check if a mentioned PV already exists (0x80131500)
CoActiveScriptSite.cpp, 895, Test evok --> 2 PV LES MÊMES

The object "PV - N°35 - 29/04/2022 - 6 21 018 - Belmont-sur-Lausanne - Chemin des Ecaravez - Autres noms : 62101" cannot be saved. At least one object with the same metadata already exists.
Duplicate object: "PV - N°35 - 29/04/2022 - 6 21 018 - Belmont-sur-Lausanne - Chemin des Ecaravez - Autres noms : 62101" (Document, ID 1816899)

Unique Object Rule: PV Chantier
Description: Check if a mentioned PV already exists (0x80131500)
CoActiveScriptSite.cpp, 737, Test evok --> 2 PV LES MÊMES

The object "PV - N°35 - 29/04/2022 - 6 21 018 - Belmont-sur-Lausanne - Chemin des Ecaravez - Autres noms : 62101" cannot be saved. At least one object with the same metadata already exists.
Duplicate object: "PV - N°35 - 29/04/2022 - 6 21 018 - Belmont-sur-Lausanne - Chemin des Ecaravez - Autres noms : 62101" (Document, ID 1816899)

Unique Object Rule: PV Chantier
Description: Check if a mentioned PV already exists (0x80131500)
AfterCheckInChanges::MFiles.ComplianceKit.MFEventHandlerAfterCheckInChanges, 22, Test evok --> 2 PV LES MÊMES

The object "PV - N°35 - 29/04/2022 - 6 21 018 - Belmont-sur-Lausanne - Chemin des Ecaravez - Autres noms : 62101" cannot be saved. At least one object with the same metadata already exists.
Duplicate object: "PV - N°35 - 29/04/2022 - 6 21 018 - Belmont-sur-Lausanne - Chemin des Ecaravez - Autres noms : 62101" (Document, ID 1816899)

Unique Object Rule: PV Chantier
Description: Check if a mentioned PV already exists (0x80131500)
CoDynamicCLRObjectWrapper.cpp, 552, Test evok --> 2 PV LES MÊMES

The object "PV - N°35 - 29/04/2022 - 6 21 018 - Belmont-sur-Lausanne - Chemin des Ecaravez - Autres noms : 62101" cannot be saved. At least one object with the same metadata already exists.
Duplicate object: "PV - N°35 - 29/04/2022 - 6 21 018 - Belmont-sur-Lausanne - Chemin des Ecaravez - Autres noms : 62101" (Document, ID 1816899)

Unique Object Rule: PV Chantier
Description: Check if a mentioned PV already exists (0x80131500)
CoDynamicCLRObjectWrapper.cpp, 322, Test evok --> 2 PV LES MÊMES

The object "PV - N°35 - 29/04/2022 - 6 21 018 - Belmont-sur-Lausanne - Chemin des Ecaravez - Autres noms : 62101" cannot be saved. At least one object with the same metadata already exists.
Duplicate object: "PV - N°35 - 29/04/2022 - 6 21 018 - Belmont-sur-Lausanne - Chemin des Ecaravez - Autres noms : 62101" (Document, ID 1816899)

Unique Object Rule: PV Chantier
Description: Check if a mentioned PV already exists (0x80131500)
ManagedError.cpp, 150, Test evok --> 2 PV LES MÊMES

The object "PV - N°35 - 29/04/2022 - 6 21 018 - Belmont-sur-Lausanne - Chemin des Ecaravez - Autres noms : 62101" cannot be saved. At least one object with the same metadata already exists.
Duplicate object: "PV - N°35 - 29/04/2022 - 6 21 018 - Belmont-sur-Lausanne - Chemin des Ecaravez - Autres noms : 62101" (Document, ID 1816899)

Unique Object Rule: PV Chantier
Description: Check if a mentioned PV already exists (0x80131500)
VaultApplicationBase.cs, 254 (IL:98), Test evok --> 2 PV LES MÊMES

The object "PV - N°35 - 29/04/2022 - 6 21 018 - Belmont-sur-Lausanne - Chemin des Ecaravez - Autres noms : 62101" cannot be saved. At least one object with the same metadata already exists.
Duplicate object: "PV - N°35 - 29/04/2022 - 6 21 018 - Belmont-sur-Lausanne - Chemin des Ecaravez - Autres noms : 62101" (Document, ID 1816899)

Unique Object Rule: PV Chantier
Description: Check if a mentioned PV already exists (0x80131500)
VaultApplicationBase.cs, 784 (IL:1), Test evok --> 2 PV LES MÊMES

The object "PV - N°35 - 29/04/2022 - 6 21 018 - Belmont-sur-Lausanne - Chemin des Ecaravez - Autres noms : 62101" cannot be saved. At least one object with the same metadata already exists.
Duplicate object: "PV - N°35 - 29/04/2022 - 6 21 018 - Belmont-sur-Lausanne - Chemin des Ecaravez - Autres noms : 62101" (Document, ID 1816899)

Unique Object Rule: PV Chantier
Description: Check if a mentioned PV already exists (0x80131500)
VaultApplicationBase.cs, 811 (IL:101), Test evok --> 2 PV LES MÊMES

The object "PV - N°35 - 29/04/2022 - 6 21 018 - Belmont-sur-Lausanne - Chemin des Ecaravez - Autres noms : 62101" cannot be saved. At least one object with the same metadata already exists.
Duplicate object: "PV - N°35 - 29/04/2022 - 6 21 018 - Belmont-sur-Lausanne - Chemin des Ecaravez - Autres noms : 62101" (Document, ID 1816899)

Unique Object Rule: PV Chantier
Description: Check if a mentioned PV already exists (0x80131500)
MethodInfo.cs, 224 (IL:116), Test evok --> 2 PV LES MÊMES

The object "PV - N°35 - 29/04/2022 - 6 21 018 - Belmont-sur-Lausanne - Chemin des Ecaravez - Autres noms : 62101" cannot be saved. At least one object with the same metadata already exists.
Duplicate object: "PV - N°35 - 29/04/2022 - 6 21 018 - Belmont-sur-Lausanne - Chemin des Ecaravez - Autres noms : 62101" (Document, ID 1816899)

Unique Object Rule: PV Chantier
Description: Check if a mentioned PV already exists (0x80131500)
UniqueObjectEnforcementModule.cs, 64 (IL:51), Test evok --> 2 PV LES MÊMES

The object "PV - N°35 - 29/04/2022 - 6 21 018 - Belmont-sur-Lausanne - Chemin des Ecaravez - Autres noms : 62101" cannot be saved. At least one object with the same metadata already exists.
Duplicate object: "PV - N°35 - 29/04/2022 - 6 21 018 - Belmont-sur-Lausanne - Chemin des Ecaravez - Autres noms : 62101" (Document, ID 1816899)

Unique Object Rule: PV Chantier
Description: Check if a mentioned PV already exists (0x80131500)
UniqueIndex.cs, 457 (IL:119), Test evok --> 2 PV LES MÊMES

The object "PV - N°35 - 29/04/2022 - 6 21 018 - Belmont-sur-Lausanne - Chemin des Ecaravez - Autres noms : 62101" cannot be saved. At least one object with the same metadata already exists.
Duplicate object: "PV - N°35 - 29/04/2022 - 6 21 018 - Belmont-sur-Lausanne - Chemin des Ecaravez - Autres noms : 62101" (Document, ID 1816899)

Unique Object Rule: PV Chantier
Description: Check if a mentioned PV already exists (0x80131500)
(M-Files 22.4.11321.4 2022-05-02T13:27:34.683Z)

Thanks for your help

Claudio

Parents
  • 1. I don't think this is possible, you can only define the additional custom message if needed but the rest of the error cannot be modified.

    2. I don't think this is possible either, the custom message is expected to be a simple description for the user on what went wrong and what they should do and they can see the relevant object details in the standard error message above it.

Reply
  • 1. I don't think this is possible, you can only define the additional custom message if needed but the rest of the error cannot be modified.

    2. I don't think this is possible either, the custom message is expected to be a simple description for the user on what went wrong and what they should do and they can see the relevant object details in the standard error message above it.

Children