Support & frequently asked questions

Yes. In CRMScript that would mean to manually call the API using the HTTP class, that does entail manually creating request and response structs for each API call

Not being technical at all, I think it is a technical issue. I think the result of a combined selection only provides you with a "view" of data, while dashboards are based on data from tables. I don´t think dashboards can view data which is from a view...

How to enable EventLog logging for Replication The Replication Client is configured to log to the Windows Event Viewer *by default* when running on a Windows operating system. Here is how it works and how you can further configure it: Where to find the logs By default, the client writes logs to: *Event Viewer* -> *Windows Logs* -> Application The *Source* will typically be `SuperOffice Replication Client` (or `.NET Runtime` for low-level crash events). This is especially useful when you have installed the client as a background service using the `Replication.Client.exe install` command. How to configure log levels (Verbosity) You can control what gets logged to the Event Viewer by modifying the `Logging` section in your `appsettings.json` file. To specifically configure the Event Log separately from the Console output, you can add an `EventLog` section like this: { "Logging": { "EventLog": { "LogLevel": { "Default": "Information", "Microsoft": "Warning", "Microsoft.Hosting.Lifetime": "Information" } }, "LogLevel": { "Default": "Information" } }, "ReplicationClient": { // ... rest of your config } }   Default: "Information": Logs general progress, start/stop events, and errors. Default: "Warning": Only logs warnings, errors, and critical failures (good for reducing noise).