2/23/2025 4:59:29 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 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.
|
|
|
|
AccountingUserID Field Usage in SLX Web 7.2
Posted: 10 Jul 08 3:56 PM
|
For Dynalink v7.0, part of the implementation calls for setting up MAS-SLX users by entering the installation path for MAS in the Accounting ID field on the SLX user profile. This field is the (string type) UserInfo:AccountingUserID field in the database.
In SLX Web 7.2 that UserInfo:AccountingUserID field is a property that is not "included" in the userInfo entity in AA; as are all other ID fields (several addressID fields and the userID field - BUT they are all SLX standardID data types) in that entity. "Including" any of these fields (then CTRL-Build Interfaces, Build and Deploy web) causes the Web client to throw an app error:- "Exception Details: System.TypeLoadException: Method 'get_AccountingUserId' in type 'Sage.SalesLogix.Security.UserInfo' from assembly 'Sage.SalesLogix.Security, Version=7.2.2.1871, Culture=neutral, PublicKeyToken=null' does not have an implementation."
My main question:
Does anyone know what this really means, or how to resolve it? Is there more to "including" entity properties that are not included ootb? What I'm trying to achieve is to code a simple business rule that says if the current user is a MAS/SLX user (userinfo. accountingID contains MAS install path) then show certain fields on this form...or not.
Note:
I observed that there is a defined relationship between the User and Userinfo tables called AccountingUser but it is based on (UserInfo.AccountingUserID to User.AdminRole); i.e., joining a text type field to a standardID type field. Seems the idea is that the userInfo.AccountingID field is meant to be used with SLX Admin Roles somehow? It would make sense that the UserInfo.AccountingUser relationship is supposed to be used in lieu of the userInfo.AccountingID field but it doesn't look like that join relationship should work, AND what about Dynalink which uses that userInfo.AccountingID field (with a text value)?
Any one observed this or have any ideas? |
|
|
|
Re: AccountingUserID Field Usage in SLX Web 7.2
Posted: 10 Jul 08 5:27 PM
|
It is good practice to hide the ID properties used for relationships so the relationship is used instead of the string id property. KWIM?
For your purpose, couldn't you use the following (didn't test this or anything)?
SLXUserService svc = (SLXUserService)ApplicationContext.Current.Services.Get<IUserService>();
IUser user = svc.GetUser();
if (user.UserInfo.AccountingUser == null)
{
// not an accounting user
}
else
{
// is an accounting user
}
or something?  |
|
|
|
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!
|
|
|
|
|
|
|
|