Epicor Functions Libraries Cannot be Transferred through Solution Workbench

Kinetic ERP
,
1

Dear All,

I hope all is well.

I created a solution where I added 3 EFx Libraries to be transferred to Cloud environment.

When I install the solution on the cloud, I get the below error:

[1/22/2024 2:45:48 PM] Processing Epicor Function definitions...
[1/22/2024 2:45:48 PM] Error A library backup cannot be used as an installation source
[1/22/2024 2:45:48 PM] Error Import cancelled or failed for 'Utility_5b55a98fbbb84397951bb0cd00c9aec0'.
[1/22/2024 2:45:48 PM] Error A library backup cannot be used as an installation source
[1/22/2024 2:45:48 PM] Error Import cancelled or failed for 'POLib_60e2bbf852f54429a181b0e600e02d55'.
[1/22/2024 2:45:48 PM] Error A library backup cannot be used as an installation source
[1/22/2024 2:45:48 PM] Error Import cancelled or failed for 'Transactions_938e57fcd9514ecba6b1b0eb0108d055'.
[1/22/2024 2:45:48 PM] Finished importing Epicor Function definitions.

Error Summary:  
Import cancelled or failed for 'Utility_5b55a98fbbb84397951bb0cd00c9aec0'.
Import cancelled or failed for 'POLib_60e2bbf852f54429a181b0e600e02d55'.
Import cancelled or failed for 'Transactions_938e57fcd9514ecba6b1b0eb0108d055'.

Anyone encountered this before?

Kind Regards.

2

Yeah, I’ve seen all sorts of weirdness with Functions and Solution Workbench… It has led me to only use Export/Import for each library.

3

But it exports it as readonly, and I want it editable. What to do?

4

What option did you choose in Solution Workbench when creating the cab file from the source environment?

5

Editable.

6

I’ve never run into an Export / Import function being read only. Under the security tab, do you have it shared with any group?

7

Are you exporting as Json or Binary?

image

I seem to recall a discussion that efxb imports were not editable… :thinking:

8

We use solution workbench all the time for functions. You must be doing something different. Permissions for functions can trip you up pretty easily across difference environments though.

9

I’m gonna try a couple of testing scenarios to see if there is any issue with the settings.

10

I found with functions, I had to set the solution type to ALL when saving the solution. Also, make sure you’re set up with the correct security groups in both environments - there are 3 groups you need on your security record.

11

I already I had my solution type to ALL and have the 3 security groups assigned, but still the same problem.

12

One thing I want to add though, the version I’m working on is 4.2.300 while the cloud version is 4.2.400, does that make any difference?

13

They work fine in 2022 but are broken when importing into 2023.2 that we noticed. So in that case Export it via Function Maintenance and Import via Function Maintenance, I think its a bug - we noticed that too @jgiese.wci and I

image

1 Like
14

Thanks for letting me know, I guess I’ll have to wait until they find a fix for it.