Risk Analysis - Best Practice help / ideas - InfoPath Dev
in

InfoPath Dev

Risk Analysis - Best Practice help / ideas

Last post 02-27-2017 08:30 AM by Hilary Stoupa. 16 replies.
Page 2 of 2 (17 items) < Previous 1 2
Sort Posts: Previous Next
  • 02-27-2017 08:23 AM In reply to

    Re: Risk Analysis - Best Practice help / ideas

     Hilary,

    I need to send you some flowers and chocolates (If I could, I would)

    Panic over - (and It was a panic!!) we just started as a site to use the form and this happened. I've found the problem. I never have "current" in the repeating table result field.  

    Result[Probability = current()/../cmbMethodOfWorkO1 and Severity = current()/../cmbMethodOfWorkE1] 

    I had something like this: Result[Probability = ()/../cmbMethodOfWorkO1 and Severity = ()/../cmbMethodOfWorkE1] 

    Fortunately,  I had one set of repeating data that worked fine and 5 tables that didn't so had something to compare with.

    Its a pity the screen shots haven't come through - This could have shown any other people how to fix the issue.

    Thanks Hilary for your speed response - 

    Best wishes

    Mike

    x  

     

  • 02-27-2017 08:30 AM In reply to

    Re: Risk Analysis - Best Practice help / ideas

    Just an FYI - you may have very well had current() and then made a minor modification to your schema. InfoPath sometimes (I have not yet tracked down when or why, but I think it is when a field is added) REMOVES current() from more complicated formulas like this. It does this to make sure we all get plenty of cardio when our heart rates shoot up and to encourage problem solving. :)
    Hilary Stoupa

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