11/26/2024 5:25:45 AM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss writing script in Architect plugins for SalesLogix & general SalesLogix customization topics (for Windows client only). View the code of conduct for posting guidelines.
|
|
|
|
How to unbind a datagrid
Posted: 30 Jun 06 9:46 AM
|
fiogf49gjkf0d I've got a legacy form with an unbound datagrid. The datagrid has several tables joined together. I used the form conversion in v6.2 to convert this to an active form. When I view the SQL statement of the converted grid, it uses BindID as part of the WHERE condition: "AND (A2.CONTACTID = :BindID)". This is not in the SQL statement of the grid on the legacy form.
I also tried adding a new datagrid to this active form to see if that would get around the bind problem. When I first specified the table the grid is based on and added a Condition, the SQL showed as "SELECT A1.LITREQID FROM LITREQUEST A1 WHERE (A1.FILLUSER IS NULL OR A1.FILLUSER = '') ".
Once I joined the CONTACT table, the BindID became part of the WHERE condition as follows:
"SELECT A1.LITREQID FROM LITREQUEST A1 INNER JOIN CONTACT A2 ON (A1.CONTACTID=A2.CONTACTID) WHERE ((A1.FILLUSER IS NULL OR A1.FILLUSER = '')) AND (A2.CONTACTID = :BindID) ".
How do I get rid of "AND (A2.CONTACTID = :BindID)", but keep the rest of the SQL statement? |
|
|
|
Re: How to unbind a datagrid
Posted: 30 Jun 06 9:55 AM
|
fiogf49gjkf0d I believe it this is being picked up from the BindID property for the DataGrid. |
|
|
|
Re: How to unbind a datagrid
Posted: 30 Jun 06 10:10 AM
|
fiogf49gjkf0d Actually I found out from another source that the forms converter does not handle grids very well. And beyond that I had a misunderstanding of how to create an unbound grid from scratch where it needs to be based on multiple tables.
It's not necessary to "manually" join the tables. Instead the join is done automatically when the columns from the various tables are selected as part of the layout.
It was the "manual" join of dragging and dropping of the common id that was causing the BindID condition to get added. So, I think I'm squared away now. Thanks. |
|
|
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|