Hi,
First off I'd like to thank you for creating such a powerful and flexible component like ChronoConnectivity! I've been using ChronoForms for years but have just recently started to work with ChronoConnectivity for a particular project.
Following your tutorials I was able to easily view and edit the data from a given database table with no problem.
However the specifics of what I'm trying to do require that I'm able to edit data that is stored across 3 separate database tables. I'm sure this isn't anything unusual, but even after carefully reviewing your tutorials I can't seem to figure out what I'm doing wrong.
Here's what I'm trying to do:
I'm using a third-party ticketing system called Freestyle Support Portal. Each ticket is assigned an "id" (stored in a table called "fss_ticket_ticket" -- see attachment #1). The custom fields available to all tickets are stored in a table called "fss_field" -- see attachment #2). And finally the actual data entered into these custom fields is stored in a table called "fss_ticket_field" -- see attachment #3).
So for example:
A particular ticket for "Acme Trucking" has an id=1 (fss_ticket_ticket) and has a field (also id=1) that contains the data "123456".
How can I set up ChronoConnectivity so that I can access the "Acme Trucking" ticket and edit all its related field data?
First off I'd like to thank you for creating such a powerful and flexible component like ChronoConnectivity! I've been using ChronoForms for years but have just recently started to work with ChronoConnectivity for a particular project.
Following your tutorials I was able to easily view and edit the data from a given database table with no problem.
However the specifics of what I'm trying to do require that I'm able to edit data that is stored across 3 separate database tables. I'm sure this isn't anything unusual, but even after carefully reviewing your tutorials I can't seem to figure out what I'm doing wrong.
Here's what I'm trying to do:
I'm using a third-party ticketing system called Freestyle Support Portal. Each ticket is assigned an "id" (stored in a table called "fss_ticket_ticket" -- see attachment #1). The custom fields available to all tickets are stored in a table called "fss_field" -- see attachment #2). And finally the actual data entered into these custom fields is stored in a table called "fss_ticket_field" -- see attachment #3).
So for example:
A particular ticket for "Acme Trucking" has an id=1 (fss_ticket_ticket) and has a field (also id=1) that contains the data "123456".
How can I set up ChronoConnectivity so that I can access the "Acme Trucking" ticket and edit all its related field data?
Hi Sean,
The associated models must have the "Relative save" setting enabled, and when you process the save action, you must have the associated model's fields available under the model's title in the data array, and the primary key value must be present as well!
Regards,
Max
The associated models must have the "Relative save" setting enabled, and when you process the save action, you must have the associated model's fields available under the model's title in the data array, and the primary key value must be present as well!
Regards,
Max
This topic is locked and no more replies can be posted.
