-
What tutorial was this? I'd like to take a look. Thanks.
-
Here is a recent thread with a similar question.
-
Since it contains code, have to tried to admin deploy the form?
-
InfoPath contains a design checker which will tell you whether the form is browser compatible or not. Please look there first to see if there are ny errors or warnings in your browser enabled form.
-
Thanks for posting the additional info. If I were you I would try to publish a test form library, without workflow,
to see if the properties are being promoted correctly by InfoPath. If they are (you detect no issues), then
the problem definitely lies with the workflow. Then I would recommend you post this in the SharePoint integration forum. ...
-
Add two fields: one for minutes (int) and one for the calculation (decimal). Add a default value for the calculated field (minutes/60). Then add conditional formatting such that the calculated field is hidden when the minutes is blank, and the minutes is hidden after the user enters a value. You have two fields, but display only one at a time.
-
I believe this was addressed via a support ticket.
-
If you email the xml form it will open with whatever the user's machine is set to open xml files. You'd need to check the file association for each machine.
You can't open an xml attachment in IPFS. In order to do that, the user needs the URL that points to the browser enabled SharePoint library.
-
In the InfoPath form, are you promoting the properties (fields) you want to show in SharePoint?
-
Thanks for the screenshot. The condition looks correct.
Where is this condition set? You'll need to have the same condition on both the fields.
I would also look at the fields' data types to make sure they match exactly.