Does anyone know how to set up child table with UD Service designer? I’ve been able to create a service with a single table, but you’re supposed to be able to set up a child table. There is a video where they talk about the child table, but they jump in after it’s set up, saying “As you can see we did all of this…” which doesn’t help anyone who is trying to set it up. I can’t find anything in the help for child tables. I know I’m missing some step somewhere, and me clicking around things is just breaking things, so am probably getting some red herrings.
Does anyone have a step by step guide for creating a table and child table using the UD service designer?
We figured it out. There is a “requirement” of a table needing a prefix. Which it only needs if you are adding just a table. When you do the service, it doesn’t require that. Because of that bumper, I wasn’t understanding why I couldn’t add a table. Once we figured that out, I was able to add the child to the dataset and service, and set my relations correctly.
Ok, now I have that setup, I re-made one and it seems like it’s working. I’m working on trying to figure out how to move it from one environment to another. I’m trying to use solution workbench, but I’m getting an error with the list dataset and I’m not sure why.
So in solution workbench I have ZBODef, ZDataSet, and ZDataTable.
If I do all of these and try to import them I get this error.
[10/25/2024 4:36:54 PM] Extracting files from CAB.
[10/25/2024 4:36:54 PM] Process started at 10/25/2024 4:36:54 PM by user bvanderson.
[10/25/2024 4:36:54 PM] Processing data definitions...
[10/25/2024 4:36:54 PM] Processing definitions...
[10/25/2024 4:36:54 PM] Import was successful for 'Ice.ZDataTable_22aa8f2d-1c62-4165-8b99-0643d706860e'.
[10/25/2024 4:36:55 PM] Import was successful for 'Ice.ZDataTable_248172e6-a8a3-4445-af0c-e41cccb0b151'.
[10/25/2024 4:36:55 PM] Import was successful for 'Ice.ZDataTable_d9118e34-3769-4a80-a9c8-3404e6fee964'.
[10/25/2024 4:36:56 PM] Import was successful for 'Ice.ZDataSet_642c2a9b-7efe-4451-98a4-37816b398509'.
[10/25/2024 4:36:56 PM] Unable to process import for 'ZDataSet'
ZSubDataSet: Table invalid for this type of dataset.
ZSubDataSet:
SystemCode='ERP'
ParentDataSetID='Sgc_PGDepositHeadList_c'
DataTableSystemCode='ERP'
DataTableID='Sgc_PGDepositHeadList_c'
IsPrimaryTable='True'
GenAttachments='False'
[10/25/2024 4:36:56 PM] Import cancelled or failed for 'Ice.ZDataSet_af43b590-b301-4abd-9e91-79fd1c533389'.
[10/25/2024 4:36:56 PM] Import was successful for 'Ice.ZBODef_c58279c9-7820-4427-9fa2-0b0235f673f0'.
[10/25/2024 4:36:56 PM] Finished importing definitions.
[10/25/2024 4:36:56 PM] Finished the import of data definitions.
[10/25/2024 4:36:56 PM] Removing temporary files.
[10/25/2024 4:36:56 PM] Build process completed.
Error Summary:
Import cancelled or failed for 'Ice.ZDataSet_af43b590-b301-4abd-9e91-79fd1c533389'.
*** Changes included in this solution may need the "Regenerate Data Model" process run in the "Epicor Administration Console" ***
The cancelled record if the List data set. But I can’t figure out why it’s doing that. The list dataset that was created was the one that Epicor created when I used the wizard to create the service to begin with.
Does anyone have an idea what I could be doing wrong? Is there another way to package this up? Does the order matter? For example, do I need to import something, then regen, then import the rest?
I’ve been looking but I can’t find anything on transferring components for the SDK.
I don’t have anything handy but that sounds like a bug that was fixed where the list table was being treated as a DB table not a temp table. I do some digging the DB. I’ll also see about getting a parent child examples documented
23.1 I’ll try it in 24.1 and see if it works on Monday. Should I be able to import all 3 Z objects at the same time? Or does it need to be done in steps?
So I imported the SDK into 24.1, all of the parts at once, then regenerated, then generated the service, then recycled, and I didn’t get any errors. We are upgrading this weekend, so I’ll just continue to develop there.
Next question I have is, how are the input parameters determined? I thought it was related to the primary keys that you set up, but that doesn’t seem to be the case. I don’t know why it picked up InvoiceNum but nothing else here. I guess it’s not a huge deal, as I can just set the fields outside of the get new call, but what’s the point of having anything?
On the child table it’s a similar thing, it picked up 2 of them, but not the other two.
)
