I’m working with the ARForm to build a routing and am running into an issue. If I include a field in the RDD, it does not appear to select in the designer. I even went through and excluded all fields and labels and only added back in the ones that are required to run the report.
I am guessing that there are too many fields in the ARForm RDD, but don’t know how to fix or get around it.
One “gotcha” with Break Routing, is that once it is defined, you can’t change the data source. So if you make on on OrderAck, and then want to add a field, you must duplicate OrderAck (say the new one is OrderAck_001), and do the mods to OrderAck_001. But you can’t change the which RDD to use in a Report Style with an Break/Route.
So always duplicate the RDD first, and use the dup for the style that will have a Break/Route.
I’ve also found that the table has to have an inner/definition only relationship with break table used in the routing.
Sometimes you have to explicitly create the relationship even if it logically exists in the base RDD.
*PackSlip for example includes the Customer and ShipHead tables. However the relationship is not written into the RDD (Background Epicor Magic). I had some additional tables joined to Customer, but neither the Customer nor the new tables were available in APR. Added a “Definition Only” relationship between ShipHead and Customer, afterwards Customer and any Definition Only tables joined to it were available in APR.
Hi Zack,
Your post was the needle in a haystack I was searching for. My customer wants to email both the BillTo customer and the ShipTo customer with the AR Invoice. I couldn’t figure out why I couldn’t see the ShipTo.EmailAddress field in APR even though the CustomerShipTo data source existed in the ARForm RDD!
Thanks for your time and your post. Very helpful!
Kelly