I have looked at other posts, and while they were helpful, they didn’t provide the information I am looking for. In Part Advisor, we have a bunch of boxes that have an EpiBinding to JobView.(NameOfField). I am used to looking at the Field help section to design a SQL script to pull data. JobView is not a table though. I know it is a view, but how can I make a consumable, like a BAQ or SQL script in SSMS, to view that data? Just wondering if anyone knows how to handle these specific types of data that aren’t your typical Table.Field structure.
Those are calculated fields which don’t have a correspondent in the database. You won’t find those in the DB - note that DB Field there is empty.
I understand that I won’t find them, but how can I use them elsewhere, or is it even possible? Would I have to use a BPM?
I think there’s a data view created along with the form. So, if you want to use them in the same form, it won’t be a problem. If you want to use them somewhere else, I don’t think it’s possible.
It’s possible, but not necessarily easy or straightforward.
You’ll have to trace and see where the data comes from.
If you need to reference other data against it, you’ll have to either do that
with LINQ, or pull the data down to a UD table with a GetList override in a BAQ,
and then you can link against it.
Here is an example of the temp table idea:
https://www.epiusers.help/t/tutorial-using-a-ud-table-as-a-temp-table-for-external-or-generated-data-to-link-with-sql/98902
Might want to integrate some of the suggestions/enhancements later on in the thread if you go that route.
1 Like
I see you marked mine as solution, but did you check these ?
No sense going down the rabbit hole if the food is on the surface.
I did check them, and they are not in there.
You will have to dig a little for them. I usually use Job Tracker that is at the Job Level. Part advisor adds another level of fun to get to unit costs and so does subs built in house.
TLA fields are This level Actual, TLE fields are This Level Estimates, LLA, LLE are Lower level assemblies.
I’ve called bos for these to get the dataviews to use in other places. Specifically I used the quote BO to get the worksheet prices that it generates to get quantity price breaks to work. I called that in a UBAQ so it could be displayed on a dashboard. It’s kinda tedious, but depending on what you would have to calculate, sometimes it’s easier and then you know you are getting the same calculations that Epicor does.
5 Likes