Force Rule Execution - InfoPath Dev
in

InfoPath Dev

Force Rule Execution

Last post 11-26-2012 03:16 PM by Hilary Stoupa. 3 replies.
Page 1 of 1 (4 items)
Sort Posts: Previous Next
  • 11-21-2012 01:26 PM

    Force Rule Execution

     I have three controls on my form. 

    StartDate <date field>

    EndDate <date field>

    Repeating Table

     

    The repeating table has a rule/condition on it to hide rows that do not meet a certain criteria (StartDate).  If I manually change the StartDate the repeating table is updated.  If I have a form load rule set the StartDate the Repeating Table is not updated until I manually set the StartDate again and exit the field.

    Is it possible to force the Repeating Table to update through configuration or code (possibly through changed event)?

  • 11-21-2012 02:09 PM In reply to

    I'm just wondering - when you set the start date in your load rule, are you using yyyy-MM-dd format? Because I just tried to reproduce this and could not - I've attached a sample form, save it locally, right click, select design, from there you can take a look at the logic, preview, etc. My table has 3 rows included by default, and is set to hide rows with a date less than the start, but I think the general idea is the same....
    Hilary Stoupa

  • 11-26-2012 03:10 PM In reply to

    Thank you for your reply.  I was looking at your form and realized I did not provide enough details.

    The repeating table contains fields from a calendar so the EventDate fields are DateTime.  If I was able to use only Date fields it would be fantastic.  But I cannot.

    I am using something very similar to this but I am not completely thrilled with it.

    http://www.manjuke.com/2011/01/how-to-filter-data-correctly-on.html

  • 11-26-2012 03:16 PM In reply to

    So the start & end date are just date, and the repeating table is date time from a SharePoint list data connection to a calendar?
    Hilary Stoupa

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