InfoPath Dev

Are the other fields that are working also looking for the Office attribute from the User's profile? Are you writing log info from your workflow to narrow down what's failing? I'd probably start with that - log the Office from the profile & make sure it has a value. Is Office a promoted form property? Or just a regular list column? ...

If the template isn't available where the XML expects it - not to my knowledge. You can look at the XML in a text editor - the href in the mso-infoPathSolution processing-instruction will show you the expected template URL. But if they cleared their InfoPath cache - they won't have the new template cached either. You could try changing ...

This will depend on where the control is that sets the editable flag from no to yes - is it in the repeating table? Is the editable flag also in the repeating table? See attached simple sample - save locally, right click and select design and then preview. It's pretty basic, but should give the general idea :)

If the form is cached, I'd guess that the user would be able to use it. If it is not cached, I'd assume they'd get the message about the XSN not being accessible. As to why it is cached on one machine and not on the other - I'm not sure....

So - that binding complaint is generally harmless - IP has a bug, because these calculated values should not actually be bound to the control, and this can be fixed with minor XSLT mods. I've not had that error create issues for me, except if it's in a print view - blog post here: ...

Did you have a chance to look at that link? Basically, your options are: qRules / FormsViewer (my company created these products), custom code or CAML (which is outlined in the link I posted). If you are using Office 365, only FormsViewer will support this scenario.

So - you can get close to this with XPath and conditional formatting - but sorting is a whole 'nother story. It is possible to modify an XSLT to sort, but it is tricky and I'm not sure if it supported in the browser (not sure if you are using browser forms or not). Here's a sample with the data grouped - I added your data a secondary ...

Not out of the box. We usually use qRules (or FormsViewer) and offload the attachments and replace them with a URL to the file, just to keep the XMLs light (and for things like reporting, where it's nice to just have a link to the file). Or, I mean - how often does this need to be done? Getting the files out of the XML could maybe be scripted ...

You get this error on upload to Central Admin? Or when you try to open the published form? Is there a correlation error? You may need to go check in the ULS log files (unfortunately) to see if there is more info there.

So - this isn't a list form, right? Yes, when you have a field in the form showing in the library, that's called property promotion. I'd start by testing the syntax with a hard coded account id and verify that it works as anticipated. That may help you figure out the issue.