In my last article I showed how you can determine if the current user is a portal user or not. In this article we will use that to selectively apply some custom CSS to the portal only. If you’re new to applying CSS styles in Creatio, take a look this article on the topic before […]
There are likely times in Creatio when you need your code to behave differently depending on whether the current user is a full Creatio user or a portal user. This is a pretty easy thing to check. You can check if the current user is a portal user by using the following: You can also […]
We had not seen this error in the InforCRM Customer Portal until recently, and the befuddling aspect was the SLXClient attachment upload worked perfectly. The Application Architect setup was checked and IIS was setup and running with the WebDll user running the CustomerPortal application and web pool.
Here is a tip for SalesLogix web Admins. If your customers do not see their tickets in the Customer Portal you will need to change the default content
In the SalesLogix 7.2 Customer Portal, you might have the need to get or set values from the user's contact record. While the user is actually a contact, in the portal, the SLXUserService is still used to get the logged in user, however, you'll need to translate to an IContact to work with the underlying contact record.
Using 7.2.1, if you change the portal title this change does not reflect as the title of the deployed site. For example, if you change it from "Sage SalesLogix" to "SalesLogix Development System", then deploy the site, it will still show "Sage SalesLogix" as the site's title. I should mention, this was not a problem in pre-SP1 (7.2.0) systems it worked fine there.