We are trying to use PowerBi and usually we can create the query in EPICOR BAQ and copy paste the syntax into the Power Query. We have some UD fields that were created on the OrderRel table, and it is giving us some errors.
Details: “Microsoft SQL: The multi-part identifier “OrderRel_UD.CustReqDate_c” could not be bound.
Invalid column name ‘CustReqDate_c’.
Invalid column name ‘CustReqDate_c’.
Invalid column name ‘PromiseDate_c’.”
I thought if we put the _UD in front of the table that would help, now we get a different error.
Details: “Microsoft SQL: The multi-part identifier “OrderRel_UD.CustReqDate_c” could not be bound.
The multi-part identifier “OrderRel_UD.CustReqDate_c” could not be bound.
The multi-part identifier “OrderRel_UD.CustReqDate_c” could not be bound.
The multi-part identifier “OrderRel_UD.PromiseDate_c” could not be bound.”
The UD fields on E10 are actually separate tables in the database. When using Epicor, it automatically pulls this table and links it. Outside of Epicor you will have to make the link yourself. I haven’t had to do that yet, I just know that’s how it works. You will have modify your SQL to join to that table.
I heard about REST and recently saw some EPICOR info on this. So in short, I have no knowledge of REST, just that it is some sort of API. Plus, I dont know anything about API’s. +:slight_smile:
If you do use direct SQL there are views created that do this join for you. The tables used by the application are in the erp and ice schema but the views are in the dbo schema. So to get the equivalent of joining erp.orderhed to erp.orderhed_ud you can use dbo.OrderHed (view)
