"Form Name" property is promoted as Computed and breaks everything - InfoPath Dev
in

InfoPath Dev

Use our Google Custom Search for best site search results.

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

Last post 02-08-2017 11:31 AM by Arthur.Avanesyan. 18 replies.
Page 1 of 2 (19 items) 1 2 Next >
Sort Posts: Previous Next
  • 11-09-2014 09:20 AM

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

     I have successfully implemented Qdabra Leave Request form in one of my environments. "Form Name" property is promoted as "Single line of text" type and is visible under library columns.

    When I try to implement this solution in another environment, "Form Name" property is promoted as "Computed" and is not visible under library columns. I can see it only under template columns. I can open form in browser and submit it. And I see that xml file under All documents. But after that, everything is broken with this file. When I click on "View Properties", "Edit Properties", "Workflows", "Version History" and etc., I see only blank windows in browser. I disabled template, deleted content type and InfoPath columns, then uploaded template again, but the result is the same.

  • 11-11-2014 08:35 AM In reply to

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

    Haven't anyone faced this issue? 

  • 11-11-2014 08:18 PM In reply to

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

    Hi Arthur,

    I'm sorry for the delay. I will ask the solution author to respond.

    More soon,

    Patrick Halstead
    Project Manager at Qdabra
  • 11-11-2014 08:46 PM In reply to

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

     Hi Arthur,

     Sorry you're having issues. I've implemented this leave request system in both SharePoint 2010 and SharePoint 2013 scenarios with no issues. Can you give me some information about the two environments you have used?  Any major differences?

    Jennifer Lindsay
    Qdabra® Software/InfoPathDev.com
    The InfoPath Experts – Streamline data gathering to turn process into knowledge.™

  • 11-11-2014 09:29 PM In reply to

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

     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.

  • 11-11-2014 09:35 PM In reply to

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

     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.

    Jennifer Lindsay
    Qdabra® Software/InfoPathDev.com
    The InfoPath Experts – Streamline data gathering to turn process into knowledge.™

  • 11-11-2014 09:47 PM In reply to

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

     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.

  • 11-14-2014 02:57 AM In reply to

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

    Hi Jennifer

    Do you have any updated news for me? 

  • 11-17-2014 11:35 AM In reply to

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

     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? 


    Jennifer Lindsay
    Qdabra® Software/InfoPathDev.com
    The InfoPath Experts – Streamline data gathering to turn process into knowledge.™

  • 11-17-2014 12:20 PM In reply to

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

    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.

  • 11-17-2014 12:31 PM In reply to

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

     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.


    Jennifer Lindsay
    Qdabra® Software/InfoPathDev.com
    The InfoPath Experts – Streamline data gathering to turn process into knowledge.™

  • 11-17-2014 12:39 PM In reply to

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

    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. 

  • 11-18-2014 11:13 AM In reply to

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

    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. 

    Jennifer Lindsay
    Qdabra® Software/InfoPathDev.com
    The InfoPath Experts – Streamline data gathering to turn process into knowledge.™

  • 11-21-2014 11:00 AM In reply to

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

     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. 

  • 11-21-2014 11:26 AM In reply to

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

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

    Jennifer Lindsay
    Qdabra® Software/InfoPathDev.com
    The InfoPath Experts – Streamline data gathering to turn process into knowledge.™

Page 1 of 2 (19 items) 1 2 Next >
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.