Unanswered

CanvasApp import: FAILURE: There should not be more than one record matching the name, found 2 records for CanvasApp with [default component library name]

(0) Share

Report

Posted on by TrD

When importing a solution (upgrade from 1.1 to 1.2) from DEV to TEST, I get the following error message:

CanvasApp import: FAILURE: There should not be more than one record matching the name, found 2 records for CanvasApp with nameolcm_customerservicehubdefaultcommandlibrary_c0cab

I get this error with all solutions in which I have a command library (component library for form commands)...

In the past, I could import solutions with component libraries (although I think this is the first time I upgrade the solution with the component library inside it)

full disclosure: the solution is a clone of multiple patches.

Anyone having ideas on how to solve this?

Categories:

Governance & administering

I have the same question (0)

All responses (7)

Answers (0)

Sven Vervynckt 12 on at

Like (0)

Report
Copy link

Link copied!

I was experiencing this exact same issue. I did an import of my solution using the Classic layout and checked the option "Overwrite Customziations" and that seemed to have resolved the issue.

Was this reply helpful? Yes No
TrD 29 on at

Like (0)

Report
Copy link

Link copied!
Hi @joe_hannes_col

Thanks for thinking along in this issue.

@joe_hannes_col wrote:
Have you tried staging an upgrade, and then applying the upgrade?
Yes. Doesn't work:
Solution "OLN Legal Case MGNT" failed to import: CanvasApp import: FAILURE: There should not be more than one record matching the name, found 2 records for CanvasApp with nameolcm_customerservicehubdefaultcommandlibrary_c0cab

@joe_hannes_col wrote:
Is the component library also used by another solution in the target environment?
No.

I did however see that there is a further customization of the component library in the TEST (and thus PROD) environment - yes, I know, not best practice - but these do not have the same name.
However - also the solution concerning the third component library (OLNIPManagement_DefaultCommand Library) gives the same error, and there is no customization for that one.
Also: if I try to delete the unmanaged component library, deletion is refused and I get the same error messages as when I try to import

Was this reply helpful? Yes No
joe_hannes_col 1,843 Super User 2024 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Have you tried staging an upgrade, and then applying the upgrade?
Is the component library also used by another solution in the target environment?

Was this reply helpful? Yes No
TrD 29 on at

Like (0)

Report
Copy link

Link copied!

Already in production 😞

Was this reply helpful? Yes No
joe_hannes_col 1,843 Super User 2024 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hello @TrD,

Would removing the solution from the target environment, and then importing the two separate solutions, be an option, or are you already using the app productively?

Was this reply helpful? Yes No
TrD 29 on at

Like (0)

Report
Copy link

Link copied!

Thanks for the suggestions, @joe_hannes_col .

However, importing the component library through a new, separate solution leads to the same error:

Was this reply helpful? Yes No
joe_hannes_col 1,843 Super User 2024 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hello @TrD,

Have you added the component library to the solution, e.g. by clicking on "add required objects"?
If so, you could try putting the component library into a separate solution, and import this solution before you're importing the updated solution (which doesn't contain the component library anymore).

Was this reply helpful? Yes No