Hi, I’ve created a developer account to experiment with the SuperOffice Web API. I followed all the steps to register an application and connect it to the SuperOffice services. However, when I make a GET request to:   https://sod3.superoffice.com/CustXXXXX/api/v1/Document I get the following response:   { "odata.metadata" : "https://sod3.superoffice.com/Cust55171/api/v1/Archive/$metadata" , "odata.nextLink" : null , "value" : [ ] } So the API returns an empty array. I know that in my regular SuperOffice account (not the developer tenant) there are many documents present. My question: is it expected that the DevNet/developer tenant does not contain documents, or am I missing a configuration step to access them via the API? Also, if it is expected, how do I fix it? I want all my documents in my SuperOffice account to be available as usual when making API calls. Thanks in advance!

I want to retrieve documents from SuperOffice via their API. I currently have a regular SuperOffice user account, not a developer account. What do I need to do to be able to call the API with my regular account? Specifically, where can I find all the necessary values such as the base URL, authentication method, client ID, client secret, and are there any other credentials or settings required to successfully make API requests? I will be using Python/FastAPI to retrieve dcuments and store them locally. Thanks in advance.

Release Postponed: Unfortunately, the release of SuperOffice 11.6 On Site has been postponed again. We are currently investigating four critical issues that must be resolved to ensure a positive experience for our On Site customers. Given the high cost of upgrading On Site solutions, we are committed to maintaining a higher standard of quality. Current Timeline: Best-case scenario: Release during next week (Week 50, 2025) Estimated release date: 11 December 2025 Worst-case scenario: Release may be pushed to January Please note that these dates are subject to change as we continue our work across multiple teams. Impact: We recognize this delay may disrupt planned customer activities. However, delivering a stable version is our top priority, rather than releasing a version that would require immediate patching. Important Change – Active Directory Support: No AD Authentication: Version 11.6 On Site will be released without support for Microsoft Active Directory (AD) as an authentication provider . Reason: Microsoft AD is now considered an obsolete technology, making development, debugging, and testing increasingly costly and time-consuming. For Customers Using AD: If you rely on AD authentication, please wait to upgrade until a future release restores this functionality. At this time, we do not have a confirmed date for AD support in upcoming releases.

We have multiple on-prem installations where we are trying to regenerate the counters and status's via the travel gateway every night. While we can run the regeneration manually by clicking execute in the travel gateway user interface without any problems, the scheduled execution only works sporadically. On 2 of the installations the scheduled execution works 9 out of 10 times. But on the last installation i have not seen it work a single time yet.  Since i'm quite new to SuperOffice there is a probably a lot im overlooking, but my first question is for a log of somekind? So I can possibly see why the scheduled execution fails or doesn't start. And also is the travel gateway still the way to go?

Hi, Are there any plans to make template variables available for extra fields so they can be used in documents? Right now, we have to duplicate fields to UDEFS just so we can use them in documents.  

Hi, We have enabled f ederated sign-in using this guide: Register identity provider (domain name) | SuperOffice Docs The hope was to alleviate the need to remember several passwords and make SO sign in immediately because our browser already has the user signed in to their MS365 account. But unfortunately, our user needs to enter their email address every time they open SuperOffice Online to then initiate a redirect to the login screen (sometimes they even need to enter their password again). Is this really the intended functionality or are we missing a part of the setup? BR Allan

Hi, while troubleshooting an issue with persons being created twice on contacts, I noticed that the SaveContactEntity method on the ContactEntity class has started to create new persons from version 11.3. Here is a CRMScript which demonstrates the issue. On 11.2 no person is created, while on 11.3 the person is created. #setLanguageLevel 4; NSContactAgent agent; NSContactEntity contact = agent.CreateDefaultContactEntity(); contact.SetName("Dummy company"); NSPerson[] persons; NSPerson person; person.SetFirstname("Waldo"); persons.pushBack(person); contact.SetPersons(persons); contact = agent.SaveContactEntity(contact); In version 11.2 the Waldo-person was just ignored. The same issue applies to the REST API, so it's not a CRMScript issue, it's just easier to visualize with CRMScript. Is this intentional?

Hi,  we've installed 10.5.4 at an onsite customer, and have feature toggled on the NewServiceRequest feature to get the new Service UI in CRM. We've enabled single signon for login (which seems to work fine), and the server is locked down with very limited access to the internet. When opening a request we see that there is a call to /api/v1/Agents/Ticket/GetForRmUi fails with an 403 error. The header X-Errormessage says "WebException: The remote server returned an error (401) Unauthorized". My gut feeling is that the ../Agents/Ticket/GetForRmUi method is trying to reach out to the internet for some reason. I see from the documentation that is a fairly new and unstable endpoint. What could cause it to try to access the internet?