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!

Web Forums - SalesLogix Web Platform & Application Architect
Forum to discuss the use of the SalesLogix Web Platform, Client and Customer Portals, and the Application Architect (For version 7.2 and higher only). View the code of conduct for posting guidelines.

Forums RSS Feed

Back to Forum List | Back to SalesLogix Web Platform & Application Architect | New Thread

View: Search:

Author

Thread: Wrapping Provider Breaks Web Site?

Ken Poggensee
Posts: 71

Wrapping Provider Breaks Web Site? Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 08 Jul 08 5:38 PM

Slx 7.2.2

Background:
I have a 1:M off Accounts called UserAccess. It has UserID’s for those users that should be able to access the account (or affiliated data). I have a separate module that manages this table based on pre-defined territories. This all works properly.

My next step was to create a custom wrapper around the provider to limit access to TACO tables/records (and a few others) based on the current UserID being in the UserAccess table. This also works properly in the LAN client.

It is actually pretty slick in the fact that I no longer have to apply custom security on each and every view (yes I did this and it sucked). This also got me around trying to get behind the Activity views and what not. So with this security in place, when I create and activity and go to lookup accounts or contacts, it only shows me those accounts\contacts where the current user has a record in my custom UserAccess table. Works basically for all lookups, groups, just about anything including external tools like ADO-Explorer. As long as it goes through the provider it works.

Again all this work fine and dandy…

So Here’s My Problem:
As soon as I enabled this custom security (provider wrapper) it breaks the web client. I end up getting errors with the GroupBuilder module. I can log in but any time I try to go to any of the TACO views it throws an exception message on the screen saying
‘Load Group XML Failed’

The security does appear to semi-work though because other pieces that don’t use the GroupBuilder like Activities. When I go to lookup an account or contact to assign to an activity, it properly displays only those records that I (current user) should have access to.

So my question is has anybody wrapped the provider, and if so did you have any problems with it on the web?

It seems to me that if you apply custom security to the provider, it breaks the web.

Anybody have any idea or direction of where to go from here?

[Reply][Quote]

Ken Poggensee
Posts: 71

Re: Wrapping Provider Breaks Web Site? Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 08 Jul 08 5:59 PM

FYI: Just got Ryans suggestion to call this in as a web bug from the BP news group...

[Reply][Quote]

Bob (RJ)Ledger
Posts: 1103

Re: Wrapping Provider Breaks Web Site? Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 08 Jul 08 7:30 PM

Actually.. it was me in the BP .. and who also cross posted the reply to the Sahara Group as wellNG

--
RJLedger - rjlSystems
"...Customer First..."

[Reply][Quote]

Ken Poggensee
Posts: 71

Re: Wrapping Provider Breaks Web Site? Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 30 Jul 08 6:47 PM

Defect created: 1-63815
Resolved with Hot Fix 12 for 7.2 (You may need to contact support for the HF)

[Reply][Quote]

Page 1 of 1

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!

slxdeveloper.com is brought to you courtesy of Ryan Farley & Customer FX Corporation. This site, and all contents herein, are Copyright © 2025 Customer FX Corporation. The information and opinions expressed here are not endorsed by Sage Software.	code of conduct \|

page cache (param): 2/23/2025 10:58:08 PM