Hi This sounds great and something we have missed for a long time. As heavy users of Customer Service, I do hope that it will offer capabilities similar to the Outlook plugin so that we can either create a new case from a chat or add it to an existing case. Looking forward to getting this enhancement Best regards Ole

SuperOffice for Teams Save your Microsoft Teams conversations and files straight into SuperOffice – so important customer chats and documents  don't  get lost.   Pilot start: TBD   What is this pilot about?   SuperOffice for Teams connects your Microsoft Teams conversations with your CRM. Instead of searching through channels and chats to  find  what a customer said last week, you save the conversation to SuperOffice – right where it belongs.   With SuperOffice for Teams, you can:   Save messages from chats and standard channels to SuperOffice.   Save a single file from a standard channel message.   Archive a date range of messages – like "Yesterday" or "Last 7 days."   Generate an AI summary of the conversation before saving. Requires AI Labs.  

SuperOffice Online Replication allows customers to stream their CRM data from the SuperOffice cloud into their own infrastructure (SQL Server) in near real-time. Why are we running this pilot? We are launching the Replication Pilot to validate the successor to our legacy "Mirroring" solution.   This is a critical infrastructure upgrade driven by three main factors: Future-Proofing for Cloud : Legacy Mirroring is not supported in our new Azure Public Cloud (APC) environment. As SuperOffice migrates customers to APC, all Mirroring users must eventually switch to Replication to maintain access to their data. Real-Time Data: We are moving from scheduled batch updates (every ~20 minutes) to near real-time streaming. The new solution uses Change Data Capture (CDC) technology to stream changes immediately as they happen. Simplified Security: We are switching from a "Push" model to a "Pull" model. You no longer need to host a public-facing web service (WCF/IIS) or open incoming firewall ports. The new client sits safely inside your network and reaches out to us. Who can join? This pilot is designed for IT administrators and partners who are comfortable managing SQL Server infrastructure. You are a good fit if: You currently use Mirroring: We specifically need existing customers to run this new client in parallel with their old solution to verify that the data is identical. You have SQL Server resources : You must provide a local SQL Server (or Azure SQL) and have a dedicated IT resource capable of installing Windows Services and configuring connection strings. Report your interes here

Hi, I've tested out custom styling today and here's some immediate feedback: The class dropdown appears to be searchable, but the search doesn't work. There's no "button" selector in the class dropdown. I was able to select it by using ".form-form .Button" though. Some customers have multiple, often many, forms where they would want the same styling on all their forms. I think a good idea would be having a "CSS template" where you could make the CSS centrally, then select that CSS template in a dropdown list when you are configuring the form. That way you wouldn't have to copy the CSS to each form, and less technical users wouldn't have to worry about the code but instead just select the design someone has already made for them. Other than this I really liked it, and it worked well on first try! Espen 

Pilot Setup Guide: SuperOffice Database Replication Version:  1.0 (Pilot Phase) Status:  Beta / Parallel Run This document outlines the technical requirements and steps to set up the new SuperOffice Replication Pilot. Unlike the legacy "Mirroring" solution, this client uses Change Data Capture (CDC) to stream data changes from the SuperOffice Cloud (Source) to your local SQL Server (Target) in near real-time. Pilot Strategy for customers using "Database Mirror": During the pilot phase, you must run this replication client in parallel with your existing mirroring solution. Do not disable legacy mirroring until data integrity has been validated. Change Data Capture:  Enabling CDC increases the database size (approx. +20%) and transaction log usage Summary of tasks: 1. Target DB : Create a new, empty local SQL database. Create a user with db_owner privileges, add schema 2. Download : Get Replication Client zip 3. Edit : Open appsettings.json. Update ConnectionStrings to point to your local target 4. Execution (Run as Admin) Run the following commands in order via CMD/PowerShell:                       a) Link Tenant b) Initial Load c) Register Service d) Start Service SuperOffice.Online.Replication.Client.exe provision SuperOffice.Online.Replication.Client.exe sync SuperOffice.Online.Replication.Client.exe install sc start "SuperOffice Replication Client"   Task-list for the IT Administrator Prerequisites .NET 8.0 Runtime:  Ensure the target machine has the .NET 8.0 runtime installed (unless using a self-contained build). Target Database:  A local or accessible MS SQL Server instance. An empty database is recommended for the initial setup. The user provided in the connection string must have  db_owner  permissions to create tables and manage the  _ReplicationState  table. Network Access: Outgoing internet access (HTTPS on port 443) to the SuperOffice Online services and SSO providers: SuperOffice Replication Dispatcher (for provisioning/tokens). SuperOffice Replication Service (for the data stream). Administrative Rights: Required for interactive provisioning and service installation. Operating System: It is currently distributed as a standalone Windows executable and includes commands to install itself as a background Windows Service. Phase 1: Approvals & Access   Request Backend Enablement:  Submit the Pilot Entry Form to request backend preparation. Note: SuperOffice Operations must manually enable Primary Keys on the source database before you proceed. Open and submit this form   Network Configuration:  Whitelist the following hostnames for outbound traffic (HTTPS/443): id.superoffice.com  (Authentication) SSO providers if used online.superoffice.com  (Replication Stream) Phase 2: Local Environment Prep   Create Target Database:  Create a  new, empty  SQL database on your local server (or Azure SQL). Example Name:   SuperOffice_Replication   Create SQL User:  Create a dedicated SQL user for the client. Permission Requirement:  The user must have  db_owner  privileges (or minimally: Read/Write + Create Table rights).   Create SQL Schema: The Replication Client is configured to store tables using a specific prefix default: crm7. The provision step will try to create this Schema for you using the db_owner privileges. If your user need - run the following SQL query on your target database to create it manually: -- 1. Create the schema CRM7 CREATE SCHEMA [crm7] AUTHORIZATION [dbo]; -- 2. Ensure your replication user has access to it -- Replace 'YOUR_USER' with the user created in the previous step ALTER AUTHORIZATION ON SCHEMA::[crm7] TO [YOUR_USER]; read more about the schema here . Phase 3: Client Installation   Download Client: Log in to OC (with your CRM Online Admin user) https://online.superoffice.com/OC2/ If multi-tenant: Select correct tenant from drop-down top left. Go to tile "Replication" Download the Replication Client from top right (Download the old zip file)   Extract Files: Unzip the downloaded zip to a dedicated folder (e.g.,  C:\Replication\ ).   Configure Connection:  Open  appsettings.json  and update the  ConnectionStrings section. Example on how a connection string look like: "ConnectionStrings" : " Server=YOUR_SERVER;Database=YOUR_DB;User Id=YOUR_USER;Password=YOUR_PASSWORD;TrustServerCertificate=True; ", In JSON files, a single backslash is used as an "escape" character. To include a literal backslash in a JSON string, you must use a double backslash ( \\ ). Fix: Change "Server=localhost\web;..." to "Server=localhost\\web;..."   Phase 4: Activation (Provisioning) Prerequisite: Ensure you have received confirmation from the Pilot Team that Backend Enablement is complete. Performance Impact During Initial Provisioning. When running the provision command for the very first time , the client triggers the activation of Change Data Capture (CDC) on all tables in your SuperOffice Online Cloud database. Expected Behavior: This is a heavy, one-time backend operation that temporarily locks tables to update indexes. Active SuperOffice users may experience short-term performance degradation or timeouts (typically lasting 5-10 minutes). It is recommended to run this initial step outside of peak business hours. Subsequent Runs: Once CDC is enabled, running the provision command again will only verify the existing configuration and will not impact database performance. Open Command Prompt (CMD) or PowerShell as Administrator. Navigate to the installation folder. Run the provisioning command: SuperOffice.Online.Replication.Client.exe provision Authenticate: A browser window will open. Log in with your SuperOffice Administrator credentials - for your CRM Online tenant. (If multi-tenant) Select Tenant: Choose the customer tenant you wish to replicate. You should now see "Provision Replication Session" dialog in your browser. - IF NOT (ie. you where redirected wrongly to the SuperOffice client etc.) - copy the URL from command promt - and paste it into your browsers address,and press Enter to see the "Provision Replication Session" dialog. Create Session: Enter a unique name for this replication session (e.g., Pilot_Prod_Node_01), and click [Create session] button to start the provisioning.   Phase 5: Go-Live [ ] Run Initial Sync: To download the database schema and initial data load, run SuperOffice.Online.Replication.Client.exe sync Duration depends on database size. This step creates the tables in your local SQL DB. [ ] Install as Service: Register the client as a Windows Service for continuous background operation. [ ] Start Service: Start the Windows Service for continuous background operation. SuperOffice.Online.Replication.Client.exe install sc start "SuperOffice Replication Client" [ ] Verify Service is started.   Phase 6: Maintenance & Validation [ ] "Database Mirror"-customers - Data Validation: Periodically compare row counts between your legacy Mirroring database and the new Replication database to ensure integrity. [ ] Monitor Disk Space: Ensure your local server has sufficient storage for the growing database.       Important: The 7-Day Data Retention Rule Unlike the legacy mirroring solution, SuperOffice Replication streams data changes through a cloud-based message queue (Kafka). To ensure optimal performance, this queue has a strict 7-day retention limit. What you need to know: Your local Replication Client must successfully connect to the SuperOffice cloud to pull data at least once every 7 days. What happens if you are offline for >7 days? If your local server is shut down, offline, or experiences network issues for more than 7 continuous days, your unpulled data will expire and be deleted from the cloud buffer. The replication stream will break, and your client will not be able to resume. You will typically see a "500 Internal Server Error" in your Event Viewer (specifically failing on SchemaRequestBuilder.PutAsync) when the client attempts to reconnect to an expired position in the stream. How to fix an expired session:  The client cannot automatically "catch up" after the 7-day window has passed. You must initiate a full reset: Contact SuperOffice : Notify your Pilot Coordinator pilot@superooffice.com and request that we trigger the "Resend All Data" routine for your specific tenant. This resets the offsets in the cloud. Local Reset: Once SuperOffice confirms the backend has been reset, we recommend that you empty/truncate your local database. Restart Sync: Run the provision and sync commands again to perform a fresh initial data load.

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).

Hi, I’ve created some additional tables, but when I try to search for data in those tables, no search criteria are available. Has anyone experienced this issue or knows how to make the table fields appear as search criteria? I Can add data to the tables. Same if I publish table in "Find" or use it from "Custom Objects" menu. OnSite version: SuperOffice CRM OnSite 11.6 Release_OnSite_11.6_2026.01.29-01  

We are looking into a issue where a user is not able to edit Custom Objects. The user can create a Custom Object, but when trying to edit the same line, there is an error message. The user is Our Contact on the Company. The user has a role with limited Functional Rights. It works when the user is given General Administrator, but that is not an option permanently for the user. We have heard from one user, but there might be others with the same role with issues. On the Custom Object the user has the Delete Right.See screenshots for the for Functional Rights and Data Rights. Tried with different browsers, ?flush, Logged in with the same user on a different PC etc.     We have tried to create a brand new role identical to the old Role and assigned to the user, still the same issue.  In a demo we created the same role, and we are able to edit. So it seems related to the setup in this particular SuperOffice. The console just gives 500 Internal Server Error.   I have been in contact with SuperOffice Support, but they asked if i could also ask the forum. Since this feature is still in Pilot. Any tips or suggestions? Anything related to the setup of the Custom Object itself? Kontraktsinfo?

Custom styling is a new feature that gives you full control over the design of your forms.  This feature allows advanced users to apply custom CSS directly to their forms for complete flexibility.       Why are we running this pilot?   We want to understand:   👉 Do users find the feature intuitive?   👉 Can they style forms as needed?   👉 Are there improvements or feedback we should consider?   Your input will help us refine the feature before a full release.     Who can join?   Customers who want to sign up need to: ✔️ Use SuperOffice CRM Online version 11.8.   ✔️ Anyone with a Marketing license When you toggle this feature on you will need to accept the terms for SuperOffice Pilot programs, To read the terms,  click here .   Sign up for pilot programs >>   What’s in it for you?   You’ll be able to style your forms better and make them match your brand identity.     How it works   You have two ways to customize your forms:   For experienced users:  Type your CSS code directly for full control.   For less advanced users:  Select a CSS class and add your code there. This makes styling less overwhelming and gives you better control over what you’re changing.     Sign up for pilot programs >>

Hi there On Address 1 when adding a UK company, it seems to be the wrong way around. An Example below:   It reads "England's Lane 41-43" when it should read "41-43 Englands Lane"   I cannot verify it is like this for all companies entered with AI, but have noticed it enough to make this post :)