General

Re: "Form Name" property is promoted as Computed and breaks everything

Arthur.Avanesyan — Wed, 08 Feb 2017 19:31:12 GMT

Thank you, Hilary!

Second time for today you are my life saver :)

Re: "Form Name" property is promoted as Computed and breaks everything

Hilary Stoupa — Wed, 08 Feb 2017 15:42:20 GMT

Hi, Arthur - sorry we missed this question. My guess is that you need to set postback to always on your date controls to make sure the qRules command executes - that is under the control's properties on the browser tab. Usually, when a qRules command works in Filler (Preview) but not in browser, that is the first thing to check. :)

Re: "Form Name" property is promoted as Computed and breaks everything

Arthur.Avanesyan — Wed, 08 Feb 2017 05:39:07 GMT

Can anyone help me with this question?

Re: "Form Name" property is promoted as Computed and breaks everything

Arthur.Avanesyan — Mon, 30 Jan 2017 08:27:55 GMT

Hi Jennifer, After successfully using Qdabra Leave Request form for more than 2 years, I have an issue. I had created different forms based on that form for vacations, sick leaves and compensatory hours and all are working properly. But now we need to combine these forms into one. I can use the same StartDate and EndDate fields for Vacations and Sick leaves, as these are only date columns, but for Compensatory hours I need date and time fields, so I created 2 additional fields StartDateTime and EndDateTime. The problem is that DateDiff command is not working for these new fields in browser. It is working in form preview, but not working when the form template is Published through Central Administration. Is injected rule not working for newly added fields?

Re: "Form Name" property is promoted as Computed and breaks everything

JenniferLindsay — Fri, 21 Nov 2014 19:26:54 GMT

Hi Arthur, you're welcome and glad you were able to find a resolution. Thanks for posting.

Re: "Form Name" property is promoted as Computed and breaks everything

Arthur.Avanesyan — Fri, 21 Nov 2014 19:00:22 GMT

Hi Jennifer,

Finally I solved the issue. I just removed FormName field from form and corresponding rules from StartDate and ReturnDate fields. I was thinking, that it was mandatory field. After removing it the form started to work as needed. No issues. What concerns to workflows, where you used FormName field as in webinar video, I just used Name column, instead of it.

Thank you for help.

Re: "Form Name" property is promoted as Computed and breaks everything

JenniferLindsay — Tue, 18 Nov 2014 19:13:49 GMT

Ok thanks. I'm currently working on deploying your template in one of our test environments, I'll let you know when I find something else.

Re: "Form Name" property is promoted as Computed and breaks everything

Arthur.Avanesyan — Mon, 17 Nov 2014 20:39:38 GMT

Yes Full Trust security level is set for both sites and I upload template using Central Administration. I have changed security level, because I use People Picker field and it doesn't work with Claims based authentication mode without using this method of security. Full Trust is not causing any problems in my first environment.

Please, see working form attached as well.

Re: "Form Name" property is promoted as Computed and breaks everything

JenniferLindsay — Mon, 17 Nov 2014 20:31:06 GMT

Hi Arthur, I also noticed that you have the security level set to Full Trust. I just checked the original Leave Request template, and it is set to Domain. Any reason why you have changed the security level to Full Trust? Did you publish it as a Full Trust template to both SharePoint sites? You should not need to set as Full Trust to publish.

Re: "Form Name" property is promoted as Computed and breaks everything

Arthur.Avanesyan — Mon, 17 Nov 2014 20:20:29 GMT

Hi Jenifer, actually I haven't added any code to the form. Even in the attached screenshot you can see that "Remove Code" button is not active, because there is no code there. When I open your original "Webinar Leave Request" form, I see the same screen there.

Re: "Form Name" property is promoted as Computed and breaks everything

JenniferLindsay — Mon, 17 Nov 2014 19:35:22 GMT

Hi Arthur, I took a look at your form template and noticed that you have added code to the form. When you add code to an InfoPath template containing qRules, you need to follow certain guidelines outlined in the post below:

http://www.infopathdev.com/files/folders/qrules/entry56111.aspx

Can you review the documentation in that post and make sure that your code was included properly?

Re: "Form Name" property is promoted as Computed and breaks everything

Arthur.Avanesyan — Fri, 14 Nov 2014 10:57:20 GMT

Hi Jennifer

Do you have any updated news for me?

Re: "Form Name" property is promoted as Computed and breaks everything

Arthur.Avanesyan — Wed, 12 Nov 2014 05:47:32 GMT

Please, see the file attached. Even if I exclude "Form Name" property from promoted properties, this field is being created anyway and the type is computed.

Re: "Form Name" property is promoted as Computed and breaks everything

JenniferLindsay — Wed, 12 Nov 2014 05:35:59 GMT

Hi Arthur,

What specific customizations did you make to the original form template? Have you tried creating a simple test form with a few promoted properties and publishing it to both environments to see if you can duplicate the problem? Feel free to attach your customized template in your reply and I'll try to take a look sometime in the next day or so.

Re: "Form Name" property is promoted as Computed and breaks everything

Arthur.Avanesyan — Wed, 12 Nov 2014 05:29:51 GMT

Hi Jennifer,

I don't think this is related especially to leave request form. Because I customized this form for my needs and successfully implemented to my environment. Then I changed already customized form to meet the needs of the second environment and faced this issue. I had setup both SharePoint servers the same way, and both contain October 2014 CUs. Even the same Content DB was used for both, then I changed the second one to meet the needs of another company. So I don't understand what could cause such issue.