Row Already belongs to another table

Kinetic ERP
, , ,
21

Support says now the target is .9

3 Likes
22

Ugh, this killed my day on monday. I was migrating RDDs and thought they were broken unitl I found this here.
Live is still 2023 so I worked in there and moved to Pilot :slight_smile:

23

yeah, i may do this as well. I didnā€™t want to play around in LIVEā€¦ but I guess I can make a new copyā€¦ fix what I need to in LIVEā€¦ and then port it over to PILOT to continue my project.

24

Same thing we are doing but cloud goes to .8 next week so Iā€™m hoping we can get a hotfix. Completely unacceptable to not be able to modify RDDs.

25

They said it would be fixed in 2024.1.8 but it hasnā€™t been. Got a notification this morning on Problem PRB0282390 that itā€™s status had been changed to ā€œWork In Progressā€

I did find that I could add a new relationship(clicking through the errors) and set the relationship fields by selecting one of the Keys defined for the table

That bought in the Relationship Fields I was looking for. Thatā€™s the only way I was able to set them

image
image736Ɨ537 24.8 KB

2 Likes
26

You can use a UBAQ as a workaround to make changes to RDDs that the error is preventing you from doing in the UI.

27

Has anybody found the root of the issue and how to workaround it? Getting this error on multiple RDDs for different Customers is driving me crazy, so time consuming to manually update through a uBAQ or create it on a different environment that has not been upgraded, not to mention that even the Standard RDD displays the error so you carry it when you create a copy. I am so not looking forward for the Upgrade in Production this weekend!

28

We are getting the same in our Pilot, among many other issues. If the actual update goes as horrible as the pilot has, we are in for real trouble.

2 Likes
29

I guess itā€™s not only me with the same issue, most part of the world got issue

30

Epicor now has a fix. The cloud team deployed it in our instance this morning and we now have a working Report Data Definition Maintenance program once again. Before this, I used REST to call the BO to add the relationship fields. Its the long way 'round, but it worked.

2 Likes
31

@Andrew did you have to request the fix to be applied?

32

I sure did, Bryan - once the support rep assigned to the case made me aware. The fix was set to be included in 1.8 (as someone here pointed out), but it wasnā€™t ready in time and therefore was excluded. I do not know which update (or release) will incorporate the fix.

3 Likes
33

Just want to let you all know that @jgiese.wci and I are On Prem and doing well.

5 Likes
34

I am also on-prem but Iā€™m finding very few people willing to say that I am doing well.

2 Likes
35

Here is code that can be dropped into a function to add relationships

this.CallService<Ice.Contracts.RptDataDefSvcContract>(svc => {
  var ds = svc.GetByID("OrderAck_c");
  svc.GetNewRptRelation(ref ds, "OrderAck_c");
  var newRow = ds.RptRelation.First(r => r.Added());
  newRow.RelationID = "OrderHed2InvcHead";
  newRow.Description = "OrderHed2InvcHead";
  newRow.ParentRptTableID = "OrderHed";
  newRow.ChildRptTableID = "InvcHead";
  newRow.JoinType = "Ouputy";
  svc.Update(ref ds);
  svc.GetNewRptRelationField(ref ds, "OrderAck_c", "OrderHed2InvcHead");
  var newRow2 = ds.RptRelationField.First(r => r.Added());
  newRow2.ParentFieldName = "Company";
  newRow2.ChildFieldName = "Company";
  newRow2.CompOp = "=";
  svc.Update(ref ds);
  svc.GetNewRptRelationField(ref ds, "OrderAck_c", "OrderHed2InvcHead");
  newRow2 = ds.RptRelationField.First(r => r.Added());
  newRow2.ParentFieldName = "OrderNum";
  newRow2.ChildFieldName = "OrderNum";
  newRow2.CompOp = "=";
  svc.Update(ref ds);
});

Also, does anyone know if this has actually been fixed yet in a newer release?

3 Likes