InfoPath Dev

Can't do that with buttons unless you use qRules command to open link in separate browser. The easy solution for you is to just use a static link in the view. Click on Insert and add a link. This link properties can be configured to have descriptive text and a separate hyperlink.

That's weird. It shouldn't be view specific. Is this the browser? If so, have you tried just turning off the ribbon altogether. We recommend doing that to reduce user confusion about what to do. The other workaround would be to use one view with hide-show sections. You can copy your existing views into the main view and add conditional ...

There definitely is code somewhere in the 50k+ posts of this forum that deal with this. Just a matter of hunting it down.

Hi Adam, Thanks! You can switch to a separate view that uses calculated values in place of text fields which may make the formatting better. The other tip is to remove all cell padding from your tables. InfoPath emails WordML structure so it doesn't surprise me that Gmail doesn't grok it. Sorry about that.

Sí, usted debería ser capaz de hacer esto.  

Hi Lockettc and welcome! You could do this quite easily with qRules SetValue command and that does work in the browser, but it requires the sandbox. I've sent your query to one of our MVPs (Jimmy) to see if he can give you the right incantation. It should be doable via the manifest.xsf, but that probably won't work for browser forms. ...

Yep, picture buttons don't have a label. And the Starter Form Hide-Show doesn't either. It is using wingdings font to show a downward pointing arrow that looks like a picture, but it is actually a font.

Are you using Content Types? If not, I would try that first and map the promoted properties to site columns. The problem with form libraries is that each column has a unique GUID per that form library. Content types use site columns which are not specific to form libraries.

Hi Yoshi, Sorry for assuming that you were "free-loading" and asking us to answer a post by one of the competing web sites. We get a lot of people who do ask us to debug Sancia's stuff (S.Y.M. Wongaton) and we have grown wary of it especially since she doesn't do best practice stuff (i.e. she recommends code too much when it ...

It may have to do with the form name. You have the form in two locations but with the same name. You should have been careful to rename the form name when you published to the new location - File -> Form Template Properties -> Name. Please try renaming the form and republishing. If that doesn't fix the issue, please reply all. My ...