Identifying Delete Operation in Repeating table - InfoPath Dev
in

InfoPath Dev

Identifying Delete Operation in Repeating table

Last post 05-25-2005 12:47 PM by Agni Jonnalagadda. 2 replies.
Page 1 of 1 (3 items)
Sort Posts: Previous Next
  • 05-24-2005 03:14 AM

    • amish
    • Not Ranked
    • Joined on 12-24-2004
    • India
    • Posts 19

    Identifying Delete Operation in Repeating table

    Hi,
    I have a Repeating table in which user can Add/Delete rows.

    Is it possible through scripting to identify if "Delete" or "Insert" Row was performed ?
    This is because based on above condition(Row added/deleted) i need to decide on some complex calculations.

    Or Is there any workaround to identify if a row was added/Row was deleted ?

    Amish
  • 05-24-2005 04:03 AM In reply to

    • amish
    • Not Ranked
    • Joined on 12-24-2004
    • India
    • Posts 19

    Re: Identifying Delete Operation in Repeating table

    Yes ,We can identify the kind of operation that takes place using "Operation" property of "eventObj" object.
    The possible values are "Insert" ,"Delete" & "Update".

    "Insert" & "Delete" values are triggered but i was not able to trigger the Update event .

    Infact when u chage a value in one of the textbox for which we have written an event procedure ,it first triggers "Delete" operation followed by "Insert" operation.
    Shouldn't it trigger an "Update" triger ?

    Can anyone tell me when "Update" operation is triggered in such scenario?


    Amish
  • 05-25-2005 12:47 PM In reply to

    Re: Identifying Delete Operation in Repeating table

    Hi Amish, Thanks for the Info.
    We used "Insert" and "Delete" operations, but we have not come across "Update" operation till now. I vaguely remember somebody telling me that "Update" operation is there but will not occur at any point of time.
    Please let us know if you have any additional info.

    Thanks!

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