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
-
Tony YatesStaff
Hi Dmitry Kuskov , Thank you for reporting this issue, and we have discovered why this happened. Here is a download link to obtain the SuperOffice.Services.WcfProxy.dll for 11.6.1004 . We have corrected for the next onsite release.
24 Feb 2026 | 09:19 AM -
Margrethe RomnesStaff
https://status.superoffice.com/incidents/s80kbz0024d7
20 Feb 2026 | 12:44 PM -
David HollegienPartner
How are they retrieving those companies from SuperOffice? Since SuperOffice shouldn't care if it is 1760-01-01 00:00:00.000 or null in the deleted date field as value.
17 Feb 2026 | 12:18 PM -
Martin AndersenPartner
Yes, you are right. Thank you. I found the help I needed here: https://docs.superoffice.com/en/api/netserver/archive-providers/aggregate-groupby.html I used a different approch and used a Post with body, the key is these columns: "Columns": [ "Count(documentId):HideDetail", "GroupBy(contactId):Footer,HideDetail" ] And then the restriction set on contactId = 38 The result is then (and yes the count is 39): (Just what I needed, at least almost, I would have liked a single column with the count 39, but this is good enough) [ { "EntityName": "footer:1", "PrimaryKey": 1, "ColumnData": { "GroupBy(contactId):Footer,HideDetail": { "DisplayValue": "[I:38]", "TooltipHint": "{document_id=21891}", "LinkHint": "" }, "Count(documentId):HideDetail": { "DisplayValue": "[I:39]", "TooltipHint": "", "LinkHint": "" } }, "LinkHint": "DrillDown=contactId|[I:38]§contactId_id|[I:38]", "StyleHint": "footer", "TableRight": { "Mask": "Select, Update, Insert, Delete", "Reason": "" }, "FieldProperties": {} } ]
17 Feb 2026 | 10:39 AM -
David HollegienPartner
The email_item table is used by the internal inbox functionality, it contains the emails that are directly taken from a specific users inbox, not only the one's an user archived in SuperOffice. Because of that, this table is indeed protected from searching (and propably because it can be a very large table). SuperOffice does not store the content of archived emails/documents in the database, but in the external document archive, which in Online can be either Azure blob storage or Microsoft 365 sharepoint. It isn't possible to query this storage directly to get the email body's.
17 Feb 2026 | 09:51 AM
Technical blog posts
Developer 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 PereraDeveloper Portal - 2.5 Release
Developer Portal – Community Release – 2. 5 Hello, SuperOffice Developers! We are ready to announce the release of Developer Portal 2.5! This version introduced a completely revamped permission model, providing site administrators more flexibility and control when assigning roles. What’s New Revamped Permission Model Flexible 🛠️ Role Assignment – Assign roles at a more granular level, giving admins better control over access and responsibilities. 🛠️ Simplified Management – Easier navigation and clearer definitions make managing user permissions straightforward for admins, and clearer on the profile page what roles a user is assigned . 🛠️ Improved Security – Enhanced role segregation ensures sensitive information is better protected. This new model ensures that every team member gets the right level of access—whether they’r e an ad ministrator, developer, partner or customer . Additional Updates Alongside the new permission model, we have included a number of backend improvements to ensure better performance and reliability of the Developer Portal! Made with 💚 by Developer Portal Team
Chamal Asela Perera