8/29/2025 1:33:37 PM
|
| |
| 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.
|
|
|
|
Changing group conditions on runtime
Posted: 04 Sep 09 4:03 AM
|
hi,
i am using SLX 6.2.6. I am using an account group on which i would like to change some of the where-conditions using a script (reason: the user should be able to select the needed data the group represents by clicking a button instead of having to edit the group in slx query builder)
Is there a way to do this?
I tried to read the plugin.data field and alter it, but I cant read it. Is there a special way to read those data streams? A rs.Fields("data") doesn't give readable data
Thanks for any help!
/Marty |
|
|
|
Re: Changing group conditions on runtime
Posted: 05 Sep 09 4:22 AM
|
| No, there is no way to do this. Your best bet is to design your own QB (with simple options etc) and then create temp adhoc groups based on the results of the options they select. |
|
|
|
Re: Changing group conditions on runtime
Posted: 05 Sep 09 10:58 AM
|
I wouldn't say that there is no way to do so, there are ways to do it, however there are very complex and it would require a quite extensive development effort.
If you look at the Lookup functionality on the 7.2 Web client, you will notice that it makes use of on the Fly group Modifications by changing the group definition as XML.
Now, the functionality is not built into the SLX Cilent, but rather into the GroupTranslator.dll.
Now, going back to what I mentioned on my first paragraph, you would need to have a good knowledge of Groups and how they are structured before going attempting to make any changes.
I do agree that the best way is to create a Temporary group (on the Windows client this is somewhat trivial), I wouldn't necessarily create AdHoc groups however. I would try something such as this:
' Create a Temp group of all accounts in Florida
Application.BasicFunctions.CreateTempGroup("Account", "Accts in FL", "ACCOUNTID", " IN ", "(SELECT ACCOUNTID FROM ACCOUNT A INNER JOIN ADDRESS D ON D.ADDRESSID = A.ADDRESSID WHERE D.STATE = 'FL')", ""
Application.BasicFunctions.SetCurrentClientGroup "Accts in FL" |
|
|
|
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!
|
|
|
|
|
|
|
|