LOL. I hear you. I only write queries to pull information so some employees can have custom reports. I then insert them into excel where all they have to do is hit refresh. They are never changing or looking at the code. Also, found the correct join on another thread.
left outer join Erp.table_UD on table.SysRowID = table_UD.ForeignSysRowID
Yep that’s the one.
In case anyone was wondering. The reason it did not pull the codes at first was because the codes need to be linked in the properties prior to inserting the UD column into the customization. Otherwise you will have to delete the epicombo, add the codes to it, and re add it to the customization.
@Banderson has a cool Excel workbook that does the same with REST and BAQs. If you’re nice, he might share it with you and you can avoid the direct DB access. 
! Yes, that was Andrew. Blaming it on COVID fog… 
@LexLawnjac, Here is the link to my post with some instructions on how the Excel workbook is setup and there is a demo file attached to the post you can use as a starting point.
2 Likes
I will check it out.
You can use dbo.Vendor instead of Erp.Vendor, saving some effort to join in SQL query.