[damianoskosmidis]

I have upgrade AM from version 3.0.1.7 to 3.0.1.8. and the dynaforms dependent fields dropbox , checkgroup and suggest are not working anymore .
To rule out possible incompatibilities of dynaform with 3.0.1.7, I created a new process "test" with a simple form with textbox (variable test1) field as independent and checkgroup dropbox, radio and suggest fields as dependent fields with SQL for all:
SELECT CONTACT_ID, CONTACT_NAME
FROM PMT_CONTACT
WHERE CONTACT_CATEGORY = @#test1
(the above query in 3.0.1.7 was working)

I am testing the following scenarios with textbox value to 1002:

1. CONTACT_CATEGORY = @#test1 nothing is working
2. CONTACT_CATEGORY = "@#test1" nothing is working
3. CONTACT_CATEGORY = @@test1 nothing is working
4. CONTACT_CATEGORY = 1002 . only suggest is not working

any hint?
Thanks in advance
damianos

[amosbatto]

I just checked dependent fields in PM 3.0.1.8 (new install) and they are working. Import the attached DynaForm and see if the dependent field is working that searches for users.

Check dependent field.json

(2.44 KiB) Downloaded 263 times

[imushtaque]

Hi amosbatto,

I'm having the same problem !
It's working fine with internal PM database, but not with external mySQL database which worked fine in 3.0.1.7.
I used a dropdown list to populate Employee Name from the external db; it seems populated a list taking empty spaces with no texts ! very strange !!
And dependent fields not showing any data at all !!!
Attached a screenshot....

Screen Shot 2016-06-02 at 9.52.14 AM.png (30.83 KiB) Viewed 4334 times

Please kindly help.

[amosbatto]

I just tried dependent fields with a database connection to a MySQL database and it works with PM 3.0.1.8.
What type of external database are you using and what version number?

[imushtaque]

Database server:
Server: mysql wampserver (127.0.0.1 via TCP/IP)
Server type: MySQL
Server version: 5.6.17 - MySQL Community Server (GPL)
Protocol version: 10
User: root@localhost
Server charset: UTF-8 Unicode (utf8)

[amosbatto]

What happens if you remove the dependent field from your SQL query? so you have something like

Code: Select all

SELECT X, Y FROM Z

What happens if you create a trigger and use executeQuery()?

Code: Select all

//set to the unique ID of your database connection:
$db = 'XXXXXXXXXXXXXXXXXXXXXXXXXX'; 
//change the SQL statement to match your table
$result = executeQuery("select x, y from z where a='something' ", $db);
var_dump($result);
die;

[damianoskosmidis]

I just checked dependent fields in PM 3.0.1.8 (new install) and they are working. Import the attached DynaForm and see if the dependent field is working that searches for users.

Check dependent field.json

thank you amos for responce. It seems to be OK.
Should the rows of checkgroup and radio controls be changed dynamically according to independed field value or remain the same after DynaForm is loaded ?
damianos

[amosbatto]

damianos,
The dependent field can only be: textbox, textarea, dropdown or suggest.
If it is a checkgroup or radio button, it will not work correctly. It will load a list of options when the DynaForm loads, but the options won't change when the value of the independent field changes.

[damianoskosmidis]

thank you amosbatto. it is clear.
d.