-
Hi - sorry I'm so slow to get back to you. I think I'd approach this differently - with a helper field and a repeating section. Here's a simple sample you can try to see if it works for you w/out hitting the calculation limit. Save the linked file locally. Right click, select Design, then preview and pick a date at the top. This uses ...
-
Thanks for your response, I appreciate.
I have restarted the Sharepoint server few times but not changes.
I logged in through SharePoint Designer, I saw the XSN file checked out, I checked in but it's showing the same error.
I rename the InfoPath file and tried to publish with another but still showing the .xsn file has been checked ...
-
Oh yuck. I've seen odd errors like this sometimes resolved with a machine restart... have you tried that? Have there been any changes in your SharePoint environment? I don't know that it's even possible to check out the XSN that is directly published to a library - you might need to get your SharePoint Admins involved.
-
Hello,
My InfoPath form just start showing error when I am trying to publish the update I made to the form. I have updated the form several times and no issue at all.
It's showing the following error:
InfoPath cannot save the following form: https://**********/****
The file "https://**********/****Forms/template.xsn" is ...
-
Dear All,
I need your support about Error: "A calculation in the form has not been completed. The number of calculation used for a single action exceeded maximum limit"
It only show 16 days not 30 days as calculation.
I attached my form. Please help me.
Thanks
-
Hi - you can add a new field to the form that is not displayed on the form itself, then use a rule or a default value to set to the display name for the item. In the data source task pane, select the main data sourceRight click the folder where you want the new field and select the option to add a fieldGive it a nameI'd ...
-
Hilary, again thanks for looking at the issue. Ive added another rule to the submit button to disable if the rich text field is blank (my:RequiredAction = "") which does appear to get over the issue.
-
I already resolved this issue. Thanks
-
Okay, rules don't seem to be executing on the Rich Text field when it is set to blank (which surprises me - if this will be a browser form you may want to verify you have the same behavior in the browser). So - you may just need to add another rule to specifically disable the submit button if the field is blank.
-
Okay I think I understand what mistake there was in my understanding of Lookup columns. I was thinking that a Lookup column (let's call it Column3 from MainList) could "lookup" the value of ANOTHER column from MainList (let's say Column1), look it up in AnotherList, and return AnotherList AnotherColumn. But what lookup lists ...