nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

FormAPI - reference other DCRs?

em4444

Hi-
Is there any way to use FromAPI in conjunction with a browse button to actually get some data from the browsed-to DCR, and place that in the main DCR, rather than just the vpath by default?

Find more posts tagged with

Comments

ISCBorisB

Hi-
Is there any way to use FromAPI in conjunction with a browse button to actually get some data from the browsed-to DCR, and place that in the main DCR, rather than just the vpath by default?

Sure, why not? For example, you can catch onItemChange Event and use IWDatacapture.callServer Method to parse
out the Data you need from the Target DCR. There are FormAPI Manual samples and dozens of Forum threads
discussing how to pass information to/from callServer Scripts.

em4444

ah ok-
so, basically, you browse as normal, which will fill the value of the field with the Vpath. You attach an onchange event to that field, which passes the vpath to a callServer script. Now the script runs entirely outside of TS, so you physically open the file on the filesystem, parse it, and pass bach the data you need.

Is this more or less what you were saying?

ISCBorisB

ah ok-
so, basically, you browse as normal, which will fill the value of the field with the Vpath. You attach an onchange event to that field, which passes the vpath to a callServer script. Now the script runs entirely outside of TS, so you physically open the file on the filesystem, parse it, and pass bach the data you need.

Is this more or less what you were saying?

Yes it is. Alternatively, you may use CC URL commands to manipulate FormAPI components of the Target DCR from the Source one, eg do it all in JavaScript.
Note though that this is not supported and requires that you open Target DCR Edit Window along with the Source DCR.