InfoPath Dev

Hi - can you post the exact text of the publish error? I can help you search for solutions - it isn't a situation I've run into before. :)

I wonder if this StackOverflow post might help you: https://stackoverflow.com/questions/35149949/sharepoint-2013-how-to-execute-javascript-on-postback

If the active view is the one you want to send, and it looks ok in email, you can just send it. I usually create a new view to have greater control over the end email result.

neat, I've looked into this and it may have some uses for me, but my form has 4 different views and the required information is spread across all of them. So my choice is either to attach the entire form to the email, or create a new view that compiles all the required info then have the send button work from there and include the "active ...

 Hello Hilary, I've been watching your demos on SharePoint/InfoPath for about a decade online.  I don't see any errors. I have added custom JQuery Code to add a Signature Box to an InfoPath Browser form, but when I do any postback from like a query filter or People picker selection; it defaults back to a regular textbox and the ...

Good Morning, I was wondering if anyone could explain the proper way to migrate my solution to SharePoint online. We are doing a manual migration. I have moved all my lists and libraries. The workflows did not move with the lists but I understand that is normal. However, my InfoPath forms did move over and look good however, when I try to ...

InfoPath forms can submit to email. You can send the "current view" of the form - so, in a browser form (I'm guessing this is a browser form - list form?) you should be able to switch views and send email (thus customizing what is sent).

So now I've been asked to do a bunch of these notification emails at different times for different situations, so I think I'm going to stay away from extra fields and such. I think I'm probably going to add a button on the Item menu and tie a workflow to it, means it's manual, but I can live with that. although what do you mean an ...

I think I would go with your general idea. I'd have the workflow set up to run if an item is created or modified - first step would be to check if the field is "yes" and then if it is, send the email. It shouldn't just wait. However, you may want to handle for not sending the email multiple times - like, if the form is re-opened ...