Importing Custom Processes - Process Calling Maintenance - Called From Field not populated

Epicor ERP 10
1

Just putting this one out there, but has anyone seen a situation where you go to import custom processes in Process Calling Maintenance->Actions and the resultant processes have nothing in the Called From field?

image

2

Yes @Hally

image
image.png1100×736 129 KB

3

That’s interesting. I would have thought if you were importing with the field populated from the export environment it should have imported. You could argue that it’s splitting hairs, maybe I’m just a bit OCD. Thanks for your reply.

4

are you saying that there is a Called Form value on the environment that you imported this form from?

5

If the original Process Calling record has a value specified in “Called From” and that value is not transferred via Export / Import in another system, Please call the issue into Epicor Tech Support.

6

Yes…

7

Thanks @Rich

Logging that issue in the morning, ran out of time today to do it. I did take a look on Epicare and nothing showed from a quick search. It’s one of those not a highly used process, I suppose.

On that note does anyone know what entity I would need to configure in Solution Management to add it into a solution?

8

-just for me to know- has the program ID the same in both environments ? i.e. has not changed ?

9

The program Id was Erp.Menu.Handheld. It even shows in the XML of the export file, just does not import. The destination menuIDs were created prior to import.

10

please forgive my ignorance, just wanted to be sure that both environment has got the same Process Key and Calling App ID’s

image
image.png995×673 32 KB

image
image.png799×573 17.3 KB

11

Here’s a snippet from the export file

 <XRefference>
    <ProcessKey>HHMN1001 </ProcessKey>
    <MenuID>UDHH001</MenuID>
    <AssemblyName>Erp.Menu.Handheld</AssemblyName>
    <SysRowID>aff9a596-8797-4bf0-93ef-eaaf9e305f88</SysRowID>
  </XRefference>

So we can see the AssemblyName has a value, but that never gets imported in. In this instance you will see that the Process Key and the AssemblyName don’t match.

Logging with @epicor this morning.

12

What version are you running?
I ran in to a similar problem in an early 10.2.200 version and was fixed in 10.2.200.17 see SCRs ERPS-98376 / ERPS-9732

13

Thanks for pointing that out @GaryWarn

On 10.1.600, but we are arranging to upgrade to 10.2.300 or 400. I’ll test on my 10.2.300 environment and see how I go.