Are the editable row's insert/delete function connected to the database? If I click the add button, is that row being added into the database? If not, how can I make it do so?
When you are interacting with an editable table on the screen (using the insert/edit/delete functions) this is only making the changes on the client. It is up to you to store this information permanently (eg in a database) using rules in the controller when a save type operation is performed.
I think you should be able to find a few different examples in the forum that cover hooking this up to a database, but the following link might be a good one to start with: http://www.hyfinity.com/node/114
I hope this is useful. Please let me know if you have any questions.
Thank you!
I looked at the example that was attached to the thread you included.
I have a question though. Since I'm trying to add an editable table with information from the database, I drag the editable table onto my screen, and go to Data Source -> SQL -> I select the table -> List all records and drag it onto the repeating section (by clicking the merge option).
When I see my page though, the insert/delete/edit buttons are not there.
How do I make it so that the editable tables have the fields from the db and keep the buttons on the table?
I'm sorry - I was actually able to find out how to keep the buttons there on the editable tables. My new question is the example that you attached to the thread you posted - the editable table example. I followed the example exactly, changing the names of the db columns: 1. added the js file to the controller, added the button, and the hidden variable. It actually is showing No Data Found and the only method that's being called is the COMMIT action.
I couldn't identify exactly where your issue arises, on the client or the server. Did you mean you added the js file to the page rather than controller?
If you are receiving "No Data Found" then the table probably couldn't bind to a data fragment at runtime. When you mention only the COMMIT action was called, are your viewing this on the Debugger trace? Is it likely that there is a pre-condition on one or more of your controller rules prior to this COMMIT that is not matching and therefore not being triggered? If this is the case then it could be that the browser is not sending the correct data through the specified bindings or the rule is not being fired due to some other mismatch. It could also be that the SQL Query prior to the COMMIT is failing to return any data. You should be able to trace this step-by-step using the Debugger.
RE: Editable Table
When you are interacting with an editable table on the screen (using the insert/edit/delete functions) this is only making the changes on the client. It is up to you to store this information permanently (eg in a database) using rules in the controller when a save type operation is performed.
I think you should be able to find a few different examples in the forum that cover hooking this up to a database, but the following link might be a good one to start with: http://www.hyfinity.com/node/114
I hope this is useful. Please let me know if you have any questions.
Regards,
Gerard
RE: Editable Table
I looked at the example that was attached to the thread you included.
I have a question though. Since I'm trying to add an editable table with information from the database, I drag the editable table onto my screen, and go to Data Source -> SQL -> I select the table -> List all records and drag it onto the repeating section (by clicking the merge option).
When I see my page though, the insert/delete/edit buttons are not there.
How do I make it so that the editable tables have the fields from the db and keep the buttons on the table?
RE: Editable Table
RE: Editable Table
I couldn't identify exactly where your issue arises, on the client or the server. Did you mean you added the js file to the page rather than controller?
If you are receiving "No Data Found" then the table probably couldn't bind to a data fragment at runtime. When you mention only the COMMIT action was called, are your viewing this on the Debugger trace? Is it likely that there is a pre-condition on one or more of your controller rules prior to this COMMIT that is not matching and therefore not being triggered? If this is the case then it could be that the browser is not sending the correct data through the specified bindings or the rule is not being fired due to some other mismatch. It could also be that the SQL Query prior to the COMMIT is failing to return any data. You should be able to trace this step-by-step using the Debugger.
Apologies if I misunderstood your query.
Regards
Abdul