Hi Epicor community,
Need some advise on ssrs reporting, after the update from epicor, my AR Form customize report are unable to generate, before the update can generate normally, so when I checked the RDD is shows this error
issue is error between invcHead and OrderHed.
Appreciate your help on this!
I would say you will have to take the base RDD and reapply your changes to create a new one. Then use your new one against your custom report style.
Can you share your screen shots of the Report style that relates to the problematic RDD?
So there would normally be an RDD named AR_Form. You should be able to copy that using the Actions Menu, then re-add the changes from your V03.
I see, Ok will try readding the changes, thanks!
I think that’s my mistake. The RDD is ARInvoice in 2023 also…
I’d have to go back and check earlier versions…to workout when it changed.
EDIT
Dug into this a bit more. The RDD for ARForm and ARInvoice exist in both 2023 and 2024.
When I look at the report styles it looks like ARForm is used on CSF and eInvoices reports ARInvoice is used for standard AR_Form Report style.
Being from where I am I have always seen ARForm.
I hope that clarifies things.
@Ziqqie_ringstorm Make sure you confirm the RDD on the base report style you are using or you might burn a heap of time.
Wait, does that mean there is another AR invoice?? Ok I need to check again
It depends if you are running a CSF, and/or your version.
Easiest way is to just load up your report style and check the rdd on the system report style…
Other thing you can do is work backwards on your rdd and look at the value of duplicate of field of the SO_ARForm_V2 rdd is and so on until you hit the system RDD.
Hope that helps
I’m running into this also. And I took the steps of trying to recreate the RDD from the base version and the issue presents itself the second I try to create a relationship with InvcDtl and OrderHed. It appears to be an impasse for right now.
One “workaround” that I’m tinkering with is you can still create a new relationship in the application and then using a UBAQ, you can add the relationship fields and it seems to accept them that way. But there were so many fields that disappeared I am still working on trying to clean up the RDL and match it with the new RDD created from the new base report.
I tried link with the ARInvoice but still showed error “row already belongs to another table” I told the finance team use to original report 1st until I can solve this custom report
Just curious reading through…
Your SD_ARForm_V03 was initially duplicated from SD_ARForm_V2.
Does your “V2” also give you the error?
Are you getting the error when you try to run the report? Or when you open the RDD?
I’ve also added OrderHed to InvcHead and I DO NOT get an error when I open my RDD. Perhaps we slowly compare yours and mine and see if we spot any differences that may be a concern??
Hi @dcamlin my SD_ARForm_V2 is not linked yet with OrderHed yet, so when i tried to link it it shows the same error
It’s a bug - its supposed to be fixed in 2024.1.8
Thanks, I’ve been messing with this on and off all day. Glad I found this!
Not fixed as of this morning… testing 2024.1.8… still get this error. 
At this point working with RDD’s is crippled until they fix this.
Anybody else have any luck?
The PRB says “in release planning”
