back to top

Defining the Detail Report in the Common Tasks area of the SalesLogix v8 web client

In a previous post I talked about the location to define what report to run from the “Detail Report” in the Common Tasks area of the SalesLogix 7.5 web client.

 

In the SalesLogix 8.0 web client that location changed along with pretty much all of the client side libraries.  The new location where the Detail Reports are defined is now found in the database in the UserOptionDef table.  Why?  Who knows.

The settings are saved in a serialized json string.  There is no formatting in the DB values but if we look at it in readable format it looks something like this:

{“defaultDetailReports”:[

{
                            “maintable”: “ACCOUNT”,
                            “family”: “Account”,
                            “name”: “Account Detail”
                        },
                        {
                            “maintable”: “CONTACT”,
                            “family”: “Contact”,
                            “name”: “Contact Detail”
                        },
                        {
                            “maintable”: “OPPORTUNITY”,
                            “family”: “Opportunity”,
                            “name”: “Opportunity Detail”
                        },
                        {
                            “maintable”: “DEFECT”,
                            “family”: “Defect”,
                            “name”: “Support Defect”
                        },
                        {
                            “maintable”: “TICKET”,
                            “family”: “Ticket”,
                            “name”: “Support Ticket”
                        },
                        {
                            “maintable”: “SALESORDER”,
                            “family”: “Sales Order”,
                            “name”: “Sales Order Detail”
                        }

}

]}

Anyways there is no interface to change the default reports but we can change them via a SQL update statement.

Boilerplate warning: Do this only after testing in a test system first.  Running SQL on a production system without testing first can be dangerous, blah blah blah.

If we want to change the default account detail report that is run we can execute a SQL statement like this:

update useroptiondef set defvalue=replace(cast(defvalue as varchar(8000)),'”maintable”:”ACCOUNT”,”family”:”Account”,”name”:”Account Detail”‘,'”maintable”:”ACCOUNT”,”family”:”Account”,”name”:”My Report”‘)
where category=’reporting’ and name=’defaultdetailreports’

In this SQL statement we are updating the Account report from “Account Detail” to a report called “My Report”.

Note: after doing so you will need to do an IISReset as the web service that uses this information caches it on startup.

Contact Customer FX for your CRM project
We let our expertise speak for itself - let us know how our all-star team can help on your CRM project
About the Author
Kris Halsrud
Kris Halsrud
Kris Halsrud is a Senior Analyst / Developer for Customer FX Corporation.

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Infor CRM Sync for Exchange: Action Required by August 31, 2026

Using Infor CRM Sync for Exchange with Microsoft 365? Your Exchange administrator must update tenant settings by August 31, 2026 to prevent sync disruption.

[Webinar] What’s Coming Next for Infor CRM SLX and Why v10 Matters

See what’s coming next for Infor CRM SLX, including new marketing workflows, automation improvements, and reasons to consider upgrading to v10.

Disable Caching in Infor CRM SLX Web Client

In the rare case caching is causing issues in the Infor CRM SLX web client, it is possible to disable specific types of caching by making edits using Application Architect, and then deploying.

Exploring AI Options for Infor CRM v10

I've started taking a closer look at the AI capabilities built into Infor CRM v10. Over the next several posts, I'll share what I learn. From the built-in features and supported AI providers to implementation considerations, costs, and practical use cases.

Infor CRM SLX 10.0: Delegate Ownership Changes for “Everyone” Records

Learn how the new EveryoneOwnerAssignment secured action in Infor CRM SLX 10.0 allows designated users to change ownership of Everyone-owned records without requiring Administrator access.

Related Articles

Infor CRM Sync for Exchange: Action Required by August 31, 2026

Using Infor CRM Sync for Exchange with Microsoft 365? Your Exchange administrator must update tenant settings by August 31, 2026 to prevent sync disruption.

[Webinar] What’s Coming Next for Infor CRM SLX and Why v10 Matters

See what’s coming next for Infor CRM SLX, including new marketing workflows, automation improvements, and reasons to consider upgrading to v10.

Disable Caching in Infor CRM SLX Web Client

In the rare case caching is causing issues in the Infor CRM SLX web client, it is possible to disable specific types of caching by making edits using Application Architect, and then deploying.

Exploring AI Options for Infor CRM v10

I've started taking a closer look at the AI capabilities built into Infor CRM v10. Over the next several posts, I'll share what I learn. From the built-in features and supported AI providers to implementation considerations, costs, and practical use cases.

Related Videos