Hello!
I know adding the PartDtl.SysRowID field to the BAQ Search is typically how we add queries to fulfillment workbench, but I keep having issues where the queries still wont show even with this.
Is there any other conditions that have to be met in order for a query to show in fulfillment workbench?
Here’s what ours looks like, works a treat:
Possibly due to the table having an alias?
Many thanks,
Nathan
Pretty sure you got it.
His says PartDtl1.SysRowID
Hey thank you! That worked!
I ended up removing the two instances of PartDtl in the sub-queries, and replace them with one instance connected on the Top Level.
FWIW, the only reason I had two instances of PartDtl was because I’m doing a Union between two sub-queries, and I thought I saw a performance improvement when linking PartDtl to OrderDtl, as opposed to PartDtl linked to a sub-query.
(Idk, something about indexed fields retrieve data faster)
Makes sense.
Also, hello fellow michigander.
Great stuff!
If you ever can’t get away from multiple table instances, you can remove all copies of the required table then add it back to top-level query first to ensure it has the table reference without an alias. It’s a bit of a pain but it works.
Thanks,
Nathan
Good tip! Thanks Again!
Hello 
