Hi All,
@admin, could this now be realised based on my
importCSVFile &
exportCSVFile functions?
I'm sure that the functions could be a lot more elegant - any input welcome - however, I'm sure that they are a sound basis on which such features could be based.
Export: PROPOSED IMPLEMENTATION
A
checkbox option on
each grid layout fields' options to to make it exportable
Each field on the grid that is checked exportable has a checkbox in table header
A new Export checked task/button that can be added to the toolbar
Where clause could be based on filtering
Furthermore, an option in the table itself to make the entire table exportable might be useful to allow devs to set all fields (SELECT * FROM table) on particular tables as exportable
A similar method for importing maybe...?
I know that these won't be able to be fully utilised in the sandbox however, what if
limited versions of the functions were available in sandbox that only allow
2 or 3 records to be imported/export at a time - for testing only? This way, you protect the integrity of the DB/Builder application and your server resources will not be exhausted???
When the component is downloaded, files with full functions could be packaged?
Let me know what you think.
Best regards and happy cooking,
Gez
