Find answers. Get support. Join conversations.

Hi, I might totally be misunderstanding this question. But you're creating a document with CRMScript, and you want the document to be displayed in the Project card under the "Activities" pane? What is your code like? Please provide a code sample. For I would do it something like this to achieve what I think you're trying to: Integer projectId; // Id of the project NSStream docStream; // Stream content of the document NSDocumentAgent docAgent; NSDocumentEntity docEntity = docAgent.CreateDefaultDocumentEntity(); // Code to set document attributes // Connect the document to the Project NSProject project; project.SetProjectId(projectId); docEntity.SetProject(project); docEntity = docAgent.SaveDocumentEntity(docEntity); docAgent.SetDocumentStreamFromId(docEntity.GetDocumentId(), docStream);

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 

Hi, did you enable the custom objects feature toggles in the web config? (V1-V4)

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 access to: SuperOffice Replication Dispatcher (for provisioning/tokens). SuperOffice Replication Service (for the data stream). Administrative Rights: Required for interactive provisioning and service installation. 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) 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: Download the Replication Client (zip file) . (Later: Log in to OC and download)   Extract Files:  Unzip 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" : { "DefaultConnection" : " Server=YOUR_SERVER;Database=YOUR_DB;User Id=YOUR_USER;Password=YOUR_PASSWORD;TrustServerCertificate=True; " }   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. Create Session: Enter a unique name for this replication session (e.g., Pilot_Prod_Node_01).   Phase 5: Go-Live [ ] Run Initial Sync: Download the schema and initial data load. 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.

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 Espen, If you are free today, we can connect on Microsoft Teams to check on the issue. Please, let me know