I have a form that I want to create in DBa and I want to call the @Command([Compose]) from a shared action in DBa that will then garnish some field data from the open document where the action is (Similar to how it would work with @DialogBox and shared fields if possible) and populate some additional data.
Then when all is said and done I want the user to click a button on the form that mails it to DBz (The DB the doc will actually reside in) and NOT save the doc in DBa. I am doing this for a couple of reasons.
I need this to work from two DB’s - DBa above and DBb - so that the data that gets populated in DBz I can create views on and see all of the information. Also, I don’t want duplication of the data, I only need it in DBz to be able to see the big picture in the views I create, so I do not want to save anything in DBa or DBb.
So, my question(s) are:
1> Can I do this using @DialogBox? I couldn’t see a way that was easy?
2> Can I do this if I make the form a response? Since I never want to actually save the form I should never have to handle the repsonse docs in my views in DBa or DBb.
3> Is there some way of doing this that I am unaware of and should investigate?
Since @Command([Compose]) has arguments for server and database, you can write a button in DBa and just specify in the @Command that you are composing the form in DBz. The document will be saved in DBz, not in DBa, but you may have to make sure that DBa has the focus once your user finishes interacting with the form being saved.
You sure can. Since the user is already in DBa, just pass the field values through the formula language. I have done this before but it was a long time ago.
Sweeping away some cobwebs here, I seem to remember that on the document form in DBz you can set the form to inherit field values when it is composed and as long as the field names are the same & the default value on the form in DBz is the field name the value should inherit.
If that doesn’t work, play around with the FIELD reserved word and @SetField.
and field sharing