alfastic

Hi Peter,

no problem, yes it is still available, you are granted admin privileges on the site. Feel free to make changes, I moved my development to a local machine.
1. Go to Data Forms at https://dstest.feldts.de/another-test/
2. Invoke menu “Products | Add values
3. Edit any item’s relationsship => problem (1) you will see no search results
4. However, add a new relationship => you will see the listboxes pointing to an empty entry. No problem so far, but if you save it now, a row will be added which should not happen, since these fields are mandatory => problem (2)
Compare the same Data project parent/child table using wpdiehard
1. Go to https://dstest.feldts.de/home/content-conf/
2. Edit any item’s relationsships => you will see all the desired search results
3. Add a relationship => there’s no “empty” row in the listbox, mandatory fields are “respected” by the plug-in

Then check out the default template of “ds_values”:
I’m using a lookup with 2 column filtering, if you’d remove it (you may), the Data Form filtering works fine again (except of the desired filtering)

Hope, you can find something.. thanks and good luck

Hi Peter,

updated. Tested. Works as expected!
Great support from your side… and thanks for the good wishes!

All the best,
Alex.

Hi Peter,
thank you – I’m relieved, since this has a huge impact on the outcome of my project.
Thanks for your quick response, it’s highly appreciated.
Best, Alex.

Hi Peter,
Thanks, I will send you the credentials by mail.
Best, Alex.

• This reply was modified 3 years, 10 months ago by alfastic.

Hi Peter,

good to know it should work. I have tested it with these scripts:

Parent table for the n:m relationship:
CREATE TABLEds_languages`
(lang_id int(11) NOT NULL auto_increment
,lang_code varchar(2) NOT NULL
,lang_name varchar(20) NOT NULL
,PRIMARY KEY (lang_id)
) ENGINE InnoDB DEFAULT CHARACTER SET utf8 COLLATE=utf8_general_ci;`

Bridged table:
CREATE TABLEds_bridge_varcharint`
(lang_code varchar(2) NOT NULL
,tm_id int(11) NOT NULL
,PRIMARY KEY (lang_code,tm_id)
) ENGINE InnoDB DEFAULT CHARACTER SET utf8 COLLATE=utf8_general_ci;`

Child table of the n:m relationship:
CREATE TABLEds_transmaster`
(tm_id int(11) NOT NULL auto_increment
,tm_format enum(‘TST’,’TSV’) NOT NULL
,tm_name varchar(255) NOT NULL
,PRIMARY KEY (tm_id)
) ENGINE InnoDB DEFAULT CHARACTER SET utf8 COLLATE=utf8_general_ci;`

I connect them via Project Templates as follows:
Manage relationships for table ds_languages
Type: n:m
Source column name: lang_code
Target table name: ds_bridge_varcharint
Target column name: lang_code
Relation table name (only n:m): ds_translations

and:
Manage relationships for table ds_transmaster
Type: 1:n
Source column name: tm_id
Target table name: ds_bridge_varcharint
Target column name: tm_id
Relation table name (only n:m): –

As a result: there is no child table at all
Solution: Redefine lang_code as Integer and it will work.

Have a good day! Best, Alex.

Hi Peter,

Both tables are base tables in the same database, and yes I lookup for the id of the image_url. I added screenshots from the “products” table here where you can see in screenshot “imageurl_no_column-type.png” the Image URL correctly retrieved from the “Image” table via lookup (the Image column is not configured as “Image URL”). In screenshot “imageurl_as_column-type.png” you can see that the image_id is used instead when the column is configred as “Image URL”.
If you prefer to see it live, I can also give you access. Thanks in advance, Alex.

• This reply was modified 3 years, 10 months ago by alfastic.