Webmerge Integration Subform Only
Anyone using webmerge to merge a multiple subform. Have a client using this integration partner and is having a problem not submitting the entire base level form each time it is updated, they only want the subform submitted each time it is filled out, not every time the base form is updated.
Client has a main form with multiple subforms. The record is assigned multiple times to different users for additional subforms to be added and then resubmitted again.
Each subform needs to be sent to webmerge endpoint only one time, not every time the record is updated. So when a second or third subform is created all of the prior subforms are sent to the endpoint again thus creating duplicate merges.
Thanks for the follow-up Matt, a few more questions for you.
- Are the additional records made in separate subforms, or more records added to the same subform?
- Does each merge go to the same place?
- Do you have to send the merge on every upload (1 per subform).. or would you prefer not to merge until all subforms have been completed and send everything at once?
I have a few ideas, but want to see which direction you need to go.
More records are added to the same subform.
Here's an overview of the actual process.
The main form is an overview of a field job with contact info, it is assigned to a different tech every day after the initial and subsequent submissions to add various subforms that require multiple records. The one in particular we are looking to merge with webmerge is a moisture log where a tech enters moisture readings daily. The daily moisture log would then be emailed to the office via pdf upon submission through webmerge. As of now, every time the main form is submitted, every multiple subform is remerged thus creating duplicates.
The merge does go to the same place as long it is the same subform. Moisture logs, Field estimates, Work orders, etc.
They would prefer to have each subform merged daily upon every upload.
Ok, cool I think I get it now. So you only want the new additions in each section sent out.. rather than all of the records added to date?
Each different section actually creates a different document output (which includes the parent level detail) but only the new work done that day?
Hey Matt, I discussed this with a colleague of mine and we believe the way to tackle this at a high level is to have a status field inside each of your subforms (can be hidden from the users).
After a successful merge those fields would be updated with a value to indicate they have already been merged and don't get reprocessed on the next update. Using logic within the merge template to dismiss the flagged records, or another data processing solution you can only process the fresh data to populate the template as desired.
Let us know if this is something you would like help with and I would be happy to discuss in a bit more detail.
Please sign in to leave a comment.