Cannot publish because of merged print view - InfoPath Dev
in

InfoPath Dev

Use our Google Custom Search for best site search results.

Cannot publish because of merged print view

Last post 12-19-2011 09:25 PM by kameronberget. 21 replies.
Page 2 of 2 (22 items) < Previous 1 2
Sort Posts: Previous Next
  • 12-05-2011 03:21 PM In reply to

    Re: Cannot publish because of merged print view

    If GenerateGuid is failing, you may have accidentally disabled qRules in your form. Try re-injecting.
    Hilary Stoupa

  • 12-06-2011 12:45 PM In reply to

    Re: Cannot publish because of merged print view

     I tried that and my form works in the client but in the browser it does nothing.

  • 12-06-2011 01:03 PM In reply to

    Re: Cannot publish because of merged print view

     If I open the form is preview and paste the SubmitToSharePointList command or GenerateGuid command it works. If I do that same thing in the browser nothing happens. I tested these yesterday in thee browser and they all worked fine. Any idea why the command field would just stop working? Right now I am using a Submit button to set the command field value to SubmitToSharePointList /submit=SharePointListSubmit /mapping=mapping /id=my:ID

     

     

  • 12-06-2011 05:52 PM In reply to

    Re: Cannot publish because of merged print view

    You have the postback on the command node set to always? And it works when you paste the command in from preview but not when you enter the same command in the browser?

    I'd like to see your form template - can you either attach it to the Options tab or send it to Support AT Qdabra DOT com and mention this thread in the email?

    Thanks!

    Hilary Stoupa

  • 12-07-2011 07:26 AM In reply to

    Re: Cannot publish because of merged print view

     I don't actually want to have the field in the form. I did 20-30 tests last night and it worked about two times. This is in production now and I can't have this happening. I have attached a link since my form is over the limit......

     

    http://www.4shared.com/file/svnzeczs/WZ-JobsiteSafetyCheck_New.html
     

  • 12-07-2011 12:52 PM In reply to

    Re: Cannot publish because of merged print view

    I understand not wanting to have the field on the form, the purpose is to be able to set it via rules, etc.

    I do not know of a reason that the command would work sometimes, which is what I think you are saying is currently happening. I do notice on your form the Submit button does not have postback set to "always" - it would be helpful to add that.

    Could you temporarily add the Error node from the Qdabra Rules data source, and temporarily change your submit button to not close on submit, so that you could try again in the browser and see if qRules is returning any error in the instances where it fails?

    Hilary Stoupa

  • 12-19-2011 09:25 PM In reply to

    Re: Cannot publish because of merged print view

     This is fixed. The problem was due to SLL being used. To fix I created an identity in the secure store service and configured my UDCX file to sue the secure store ID.

Page 2 of 2 (22 items) < Previous 1 2
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.