SuperOffice CRM Professionals
Experienced experts in SuperOffice CRM - those primarily responsible for the setup, configuration, maintenance of SuperOffice in an organization, as well as those responsible for the implementation of applications or integrations, or provide consultancy services as to how an integration should be implemented using current industry standards.
Quick access:
Shortcuts to common tools and tasks within the Technical Center.
Latest forum posts
-
Hi Helene, Is there any current documentation on what is coming in 12.0 (that is not bugfixes) ?
12 May 2026 | 03:48 PM -
Anders LarssonPartner
Ok, strange.. Have you looked at docs here: NetServer Core API | SuperOffice Docs
12 May 2026 | 12:16 PM -
Since recently, the Outlook mail link icons are not shown anymore. It has to do with the COM add-ins that are slow running and for that reason they are disabled or inactive. I know how to activate them but every morning when I start the laptop, I have to activate them again as they are put in tot the inactive part when starting up outlook. This is only recently and I do not know what to change so that they do not dissapear every day. Ps. Using Superoffice email is not an option for me and I am using Outlook (version 2019). We are not using 365 yet. Does anybody have an answer?
12 May 2026 | 10:00 AM -
Hi, In our Service Module each Ticket we worked is also Billing to our Customer will be billed til end of the Month. We have scheduled Tasks in week Inteval and startet in all 7 days (that means daily Jobs), in Scripts it will be checked if current Date is End of the month, then run the logic to create a couple of Tickets for Partial invoicing to our Cutomer for the Tickets running over more Months, means, if the original Tickets till End of Month not be closed then transfer its Working time (UDF) as Billing amount to the new closed Tickets for the Partial invoicing and set it to zero in original Ticket where our User go on working till anytime it will be finally closed. To limit the runtime < 60 Sec., i have implemented the Scripts in 3 Scripts, in Logic I allocated to create new tickets for Partial invoicing by created date of the original tickets, then start three jobs for each Scripts at diff. Time 22:05/22:25/22:45 each with less Runtime, see below green marked Jobs. Here one Jobs in Details: The three Jobs works till now fine started correctly at diff. planed Time 22:05, 22:25, 22:45 for several Monthes, but on Apr. 30th all three jobs were started from 01:00, Date is correct, but started 21h earlier as planed, so our User missed during this day to check his Tickets which in the Evening will be partially invoiced. See here new Tickets automatically created from jobs at incorrect time. The Question is, how could we or SuperOffice make sure that all planed Jobs started at corrrect Time. We have asked our local SO Support Teams, but no Feedbacks. Thanks!
7 May 2026 | 08:42 AM -
Trevor SharpPartner
Hi Sverre, Indeed, it has been a long time, I hope you are doing well. Thanks for clarifiying this, this kind of makes sense now, every email I send via a CRM Script sets the value to 2, whereas general replies to requests are all set to 1. Thanks again, Trevor
30 Apr 2026 | 08:25 AM
Technical blog posts
Database Mirroring is evolving – Highlights from our webinar
On Wednesday we hosted a webinar to walk our customers, partners, and consultants through one of the most significant infrastructure changes we've made in years: the sunsetting of the old Database Mirroring service and the introduction of our new Replication service. We were thrilled to see over 120 people registered, and the engagement during Q&A was fantastic. Thank you to everyone who joined, and especially to those who asked such sharp and thoughtful questions — they made the session genuinely better for everyone. Why are we making this change? The old mirroring solution was built on WCF and .NET 4.8, technology Microsoft stopped supporting years ago. Beyond the technical debt, it had real security limitations: it required inbound connections, X.509 certificates with long-lived credentials, and you had to host a public web service endpoint near your database. Some of our largest customers, including DNB, raised serious concerns about running it in its current form. The new solution flips the model entirely. Your client connects outbound only — no inbound firewall rules, no certificates to manage, no IIS to maintain. Authentication uses short-lived tokens with automatic rotation, and setup takes minutes rather than days. What's new — and how fast is it? During the live demo, Ludvig showed the entire setup from scratch: downloading the client from the Operation Center, configuring a connection string, running the provisioning command, and installing it as a Windows Service. The whole process took only a few minutes. The speed difference is striking. The old service pushed data in batches every approx 20 minutes. The new Replication service syncs changes in 1–7 seconds . We saw this live during the demo — a new company created in SuperOffice appeared in the replica database within seconds. Real-world experience: How we migrated our own environment Jarle walked us through how SuperOffice migrated our own internal SuperOffice installation to the new service. His approach — setting up the new database in parallel, running both side by side, then doing a rename switch — meant that none of the existing BI tools or integrations needed their connection strings updated. A practical tip worth borrowing. He also recommended excluding very large tables you don't need, like the message table, to speed up the initial replication. For large databases, the first full sync can take several hours, so planning this outside working hours is a good idea. Key Q&A highlights The questions were excellent, and here are some of the most important answers: Will my custom fields and extra tables be replicated? Yes — the new service replicates everything the old one did, including extra tables, and respects the same exclude list you've configured in admin. Can I run old and new mirroring side by side? Yes. We recommend this approach for migration. Just remember to stop the old mirroring service before going live with the new one to avoid error message floods. When will the old service stop working? The old mirroring will stop working when we migrate the platform to Azure, which is planned for after summer, before Christmas . We don't have an exact date yet, but we encourage everyone to start migrating as soon as possible. What if the service goes down? Changes are kept in the queue for 7 days . If your client has been down for less than 7 days, it will automatically catch up when it reconnects. If it's been down longer, reach out to support. Is a cloud-native/container option coming? Not yet — but it's on the roadmap. We're working on a container-based solution, with Kubernetes as the first target. We hear the demand and are actively working on it. What you should do now The new service is live today . If you have a mirroring license, you can log into the Operation Center , find the Replication widget, and download the client right now. If you're on Visma , you can start immediately If you're on Azure or online.superoffice.com , please give us a heads up first so we can ensure you're on the right database platform and can scale resources for your initial sync Documentation on docs.superoffice.com is being updated — in the meantime, setup guides are available in the community pilot forum . The recording from the webinar is posted on Youtube . If you have follow-up questions, post them in the forum and we'll make sure they get answered. Thanks again to Jens, Ludvig, Jarle, and Frode for an excellent session — and to all of you for making the Q&A so lively. See you at the next one.
Margrethe RomnesDeveloper Portal - 2.11 Release
Hello SuperOffice Developers! We’re excited to announce the Developer Portal 2.11 release. This update focuses on improving the feedback the portal provides when partners prepare and publish their applications. The goal is to make it easier to understand what’s required and ensure that important information is in place before publishing. App Store Information v isible o nly a fter creating a Standard Application From this release for wards, partners must have at least one standard application before the App Store Information section becomes visible. If no standard application exists, the section will be hidden. This ensures the App Store profile configuration is only available when it is relevant and actionable. After creating a standard app the App Store information is visible. Required Partner Profile feedback b efore p ublishing to s tage Before a partner can request publishing to Stage , all mandatory Partner Profile fields must be completed. The system validates that the following required fields are filled: Description Meta description Version name Images Links If any required information is missing: The “Request to publish” button in the Stage environment will be disabled. A tooltip will appear with the message: “Some required profile details are missing. Please complete the missing fields and save before publishing.” This ensures that all essential profile information is in place before submitting a publish request. App Store Profile feedback b efore p ublishing to Stage The App Store profile does not include mandatory fields, but the system provides feedback through warnings and recommendations. If any warning appears on the screen : The “Request to publish” button is disabled. A tooltip provides feedback about what is missing : “Some required profile details are missing. Please complete the missing fields and save before publishing.” Once all required partner profile fields are completed, the “Request to publish” button becomes enabled . However, if the “What’s New” section or the “Release Date” field is not filled in, a Validation results modal will appear when attempting to publish. The modal will inform the user that these fields must be completed before the profile can be successfully published. Partners can then choose to : Go back and complete the additional recommended fields, or Ignore the warning and continue with the publish request. This approach highlight s important release details while still offer ing partners flexibility when appropriate . Apart from these changes, we also fixed few bugs to improve the overall experience. Thank you for using the SuperOffice Developer Portal! Build with ❤️by Developer Portal Team
Chamal Asela PereraDeveloper Portal - 2.10 Release
Hello SuperOffice Developers! We’re excited to announce the first release of the year for the Developer Portal. The Developer Portal 2. 10 release focuses on performance improvements and usability enhancements across key areas of the portal. This update makes working with tenant data faster and improves the App Store and Developer portal landing pages. Highlights in t his r elease ⚡ Faster t enant d etails e xperience Tenant information now loads more smoothly as you browse, making the Tenants page feel quicker and more responsive— especially when working with larger tenant lists. 📤 Export t enants to Excel With the new Load a l l option , you can now load and export all tenant data on the Tenants page to an Excel file. This makes it easier to review, share, and work with customer information offline. 🧭 Updated Developer Portal l anding p age & App Store The Developer Portal landing page has been refreshed to align with the new brand guideline . Finally , we have addressed and resolved several bugs to ensure a smoother user experience for both Developer Portal and App Store users. Thank you for using the SuperOffice Developer Portal! Build with ❤️by Developer Portal Team
Chamal Asela PereraDeveloper Portal - 2.9 Release
Hello SuperOffice Developers! We’re excited to announce the final Developer Portal release of the year. This update brings improved dark mode visibility across several areas of the portal, delivering better readability and a more consistent visual experience. We’ve also introduced incremental, chunk-based data loading in the Partners and Applications sections, resulting in faster load times and improved responsiveness. Additionally, the log section has been refactored to offer a cleaner and more intuitive user experience. As always, security remains a top priority, and this release includes important security fixes to further strengthen the platform. What’s New Faster Data Loading for Partners & Applications In the Partners and Applications sections, we now use a chunked data loading approach , which loads data incrementally instead of all at once. This results in significantly faster load times and smoother navigation through large lists. Export list of tenants A new export option has been introduced on the Tenants page, allowing partners to download the list of tenants who have authorized one or all of the applications for any selected environment as an Excel file . The export currently includes only the rows that are loaded and visible in the grid. Refactored Log Section The log section has been refactored to provide a cleaner and more user-friendly experience. Users can now browse and interpret logs more easily and efficiently. Improved Dark Mode Visibility We have enhanced dark mode support in various parts of the Developer Portal to ensure better readability and visual comfort for users who prefer or rely on this theme. Security Fixes This release includes important security enhancements, which improve the overall security posture of the Developer Portal. As this marks our final release for the year, we’d like to take the opportunity to thank everyone for your continued feedback and support. We hope these improvements make your experience with the Developer Portal even better, and we wish you a relaxing and enjoyable time ahead. Build with ❤️by Developer Portal Team
Chamal Asela PereraDeveloper Portal - 2.6 Release
Hello, SuperOffice Developers! We’re excited to announce the release of Developer Portal 2.6! This version focuses on enhancing the user experience with the introduction of Dark Mode , providing a more personalized and accessible workspace for all users. What’s New Dark Mode Support – A new Dark Mode option has been added to improve usability, accessibility, and personalization. Users can now toggle between Light , Dark , or System Default themes to match their preferences and working environments. Theme preferences are stored per user/session, ensuring a consistent experience. All pages, components, and widgets have been styled for theme consistency. The design complies with accessibility guidelines for contrast and readability. This update enhances readability in low-light environments, reduces eye strain, and delivers a modern user interface aligned with industry standards. Additional Updates Alongside Dark Mode, we've made a framework update as well to improve the performance and reliability of the Developer Portal. Build with ❤️by Developer Portal Team
Chamal Asela Perera