Add an update field to a repeating table - InfoPath Dev
in

InfoPath Dev

Add an update field to a repeating table

Last post 07-10-2012 04:17 AM by pelizdr. 2 replies.
Page 1 of 1 (3 items)
Sort Posts: Previous Next
  • 07-09-2012 07:06 AM

    Add an update field to a repeating table

    I am using a database connection (database template) to get all the asset records from an SQL table based on the user ID.  The problem I am having is trying to add a field to the repeating table (not from the SQL source) so the end user can update the budget code.  We do not want them writing directly to SQL, but to submit this data in an e-mail.  If I try to embed a new repeating field in the table, I either get the same field repeated for each record (changing one changes them all), or I only get one field for the first record, the rest are missing.  I tinkered with the Master/Detail options, but this is foreign territory for me.

     Any assistance would be greatly appreciated.

  • 07-09-2012 01:38 PM In reply to

    Re: Add an update field to a repeating table

    Database forms are bound (locked) to the database, which is why you've been having issues adding a field. If you look at the form's schema, you'll probably see a little lock next to each node and group.

    So, basically, if you want flexible InfoPath forms, with an unlocked and modifiable schema, you should not use a database-bound form.

    Are users just reading data from SQL or also writing?

    Ernesto Machado
    Qdabra® Software/ InfoPathDev.com
    The InfoPath Experts – Streamline data gathering to turn process into knowledge.™


  • 07-10-2012 04:17 AM In reply to

    Re: Add an update field to a repeating table

    Thanks for the response, Ernesto.  We only want the users to read the table.  The "opportunity" of using a regular form with a database connection is the amount of time it takes for the form to pull in all the data, then filter.  Using the database-bound template, the query is much faster, but I agree is limited in scope of use.  I guess the other option would be to add a field to the table and just never submit any data to it (leave the field blank and use it elsewhere).  I was trying to stay away from this option, but if it won't work any other way...

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