dynamically modify manifest.xsf - InfoPath Dev
in

InfoPath Dev

dynamically modify manifest.xsf

Last post 06-08-2006 09:17 AM by andreas.vogel. 2 replies.
Page 1 of 1 (3 items)
Sort Posts: Previous Next
  • 06-05-2006 11:13 AM

    dynamically modify manifest.xsf

    Hello,

    I'm new to infopath and to the .net world period.
    My question is: is it possible to dynamically modify the manifest.xsf?
    I'm looking to change the default value - formula of a field based on the value of another field (a drop down). Since XPath doesn't do if / else statements I was hoping there is some kind of way to modify/hack the manifest.xsf... maybe with something similar to an xsl:choose or xsl:if ?

    Rules and Validators don't fullfill my requirements. JScript on each fields action will work but will require 3 times the amount of code that it would take if I can modify the default value - formual of a field.

    Thanks,
    -Andreas
  • 06-07-2006 11:33 PM In reply to

    Re: dynamically modify manifest.xsf

    Hello,

    Did you try use conditions?
    You can set different Formulas and different conditions. Based on the changed value in the text box/drop down, appropriate condition/Formula will be fired.

    I hope this is what you are looking for.
    Kalyan G Reddy
    Infopath MVP 2007 and 2008
  • 06-08-2006 09:17 AM In reply to

    Re: dynamically modify manifest.xsf

    Hi Kalyan,

    When you say conditions, do you mean Rules?
    The problem with Rules is that it does not allow one to set the "Default" value of a field. This means that the affected field will only update when the drop down has been changed. If the formula however requires a number of other fields to be involved - anytime the other fields change - it will not reflect those changes.

    For example:

    <DropdownField> --> Rule - if text = "Foo" then set value of <someField> = <FieldA> * <FieldB> * <FieldC>

    The problem with this is - that this calculation only happens when <DropdownField> is modified...as it is not setting <someField>'s default value.

    I hope this clarifies my problem.

    Thanks,
    -Andreas



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