Hi all, I again find myself confused by an overabundance of information about a beginner’s topic.
What is the correct practice when you want to add a field to an epitextbox which is not there in the available EpiBindings? I’ve done this sort of thing with UD fields, but that was for more straightforward. Is this when you create a data view in the script editor? I’m truly sorry for this completely basic question but I have not been able to sus this out on my own.
If the specifics will help, at the moment I’m trying to add the Ship Via Code from the PO to AP Invoice Entry.
Hey Steve, thanks. I think I must be looking for Adapters then. I just want to display the ShipViaCode from the related PO on AP Invoice Entry. That actually helps narrow things down immensely, so thank you again.
Hey Kevin. After Steve’s comment I dug into the customization guide and found a couple of threads that suggested maybe I could do this with a Foreign Key View. Here’s what I tried:
This does not produce any errors, but does not seem to work. I have not had a chance to test this with a real invoice, but it does not seem to display the ShipVia if I create a test invoice and bring in a PO.
To be honest, I’ve never gotten it to work. But my boss, who is not a coder by any means, set
it up with ease. I’d love for someone to show me how and make it make sense.
You make that sound so simple haha. I must be thinking about this wrong. Should I be getting the ShipViaCode via a BPM and then putting into something accessible from the form? I’m sorry I’m dense.
Basically once you know the info you need and the basis, you decide on an adapter or a BAQ (also using an adapter, but dynamic query, because it’s faster). You parse the results from your adapter into variables and then set up the logic to make sure you have it right. Then, you assign it to the value of your control, either directly if it’s a custom control or using the csm methods if it’s a native control. It’s not easy or simple but it is logical.
By “basis” I just mean the criteria. For example, something that could be a “where” clause in a query.