Good afternoon SuperOffice, I am having a problem with the Updated Dates when accessing these in the Saas enviroment. I have read the documentation here: https://docs.superoffice.com/en/api/netserver/web-services/so-timezone.html It states that the Created and Updated dates are always in UTC, and that the SO-TimeZone header is ignored: I have been testing this in postman, and the Updated Dates I am getting back from the API call are UTC + 2Hrs. Below is an example of me update this company, as you ca see I did this at 15:11:18 (BST):   UTC for this would be 14:11:18pm, but when I call the API, I get a date of 16:11:18   I have tried to add the TimeZone header anyway, but get the same result:   Please could you advise where I am going wrong? Cheers Rich          

When configuring the SO10Web to Authenticate via Active Directory by using the <ActiveDirectoryCredentialPlugin> settings in Web.Config the system is using LDAP for communicating with AD. I got a question from the IT-department of a customer that is planning to upgrade from SuperOffice 8 to 10 (not migrating to Online yet because of some other legacy systems) - if this connection is done by LDAPS (that is with SSL). What is required to force this authentication not to be done in "plain LDAP" but to use LDAPS?  And is there a possibility to use "Signed LDAP" authentication?  Are there any configuration possibilities for this in SuperOffice itself - or do SuperOffice rely on configurations done on the Windows Server that is running the IIS? 

When a user in a marketing mail selects the checkbox "Override consent and subscription / Overstyr samtykke og abonnement".  Is this value stored in the database somewhere ? 

I apologize if this is not the appropriate forum for this query. Following a recent update to the CRMScript tracing mechanism, the debugger no longer tracks the current line of execution. As a result, during step-by-step tracing, the user must manually locate the active line in the script, which is both cumbersome and time-consuming. Could this behavior be reverted or corrected so that the trace once again follows the currently executed line?    

I'm trying to understand how the SearchEngine work. What is the difference between the 2 searchengines below? I get 2 different results. In case  In the second case I get a row, where y_eb_eval_koder.x_ft_heading == '82', which it shouldn't be allowed to.   Case 1: String null; SearchEngine se; se.addField('y_eb_eval_koder.id'); se.addField('y_eb_eval_koder.x_ft_heading'); se.addCriteria('y_eb_eval_koder.x_ft_heading', 'Equals', '80', 'And', 1); se.addCriteria('y_eb_eval_koder.x_eb_post', 'Is', null, 'Or', 2); se.addCriteria('y_eb_eval_koder.x_eb_post', 'Equals', '0', 'And', 2); se.buildSql() gives: select a0.id, a0.x_ft_heading from y_eb_eval_koder a0 where a0.x_ft_heading = ? and (a0.x_eb_post is NULL or a0.x_eb_post = ?) //reducing parantheses select a0.id, a0.x_ft_heading from y_eb_eval_koder a0 where a0.x_ft_heading = ? and (a0.x_eb_post is NULL or a0.x_eb_post = ?)   Case 2: String null; SearchEngine se; se.addField('y_eb_eval_koder.id'); se.addField('y_eb_eval_koder.x_ft_heading'); se.addCriteria('y_eb_eval_koder.x_eb_post', 'Is', null, 'Or', 1); se.addCriteria('y_eb_eval_koder.x_eb_post', 'Equals', '0', 'And', 1); se.addCriteria('y_eb_eval_koder.x_ft_heading', 'Equals', '80', 'And', 2); Using se.buildSql() and reducing parantheses again, I get this: select a0.id,a0.x_ft_heading from y_eb_eval_koder a0 where ((a0.x_eb_post is NULL or a0.x_eb_post = ?) and ((a0.x_ft_heading = ?))) //reducing parantheses select a0.id,a0.x_ft_heading from y_eb_eval_koder a0 where (a0.x_eb_post is NULL or a0.x_eb_post = ?) and a0.x_ft_heading = ?)   Trusting the printed SQL I end up with the following: Case 1 : select a0.id, a0.x_ft_heading from y_eb_eval_koder a0 where a0.x_ft_heading = ? and (a0.x_eb_post is NULL or a0.x_eb_post = ?) Case 2 : select a0.id, a0.x_ft_heading from y_eb_eval_koder a0 where (a0.x_eb_post is NULL or a0.x_eb_post = ?) and a0.x_ft_heading = ?   Isn¨t those the exact same expressions, just with the 2 where-statements switched?  

Not sure if this belongs in this forum, but: Consider a installation, planned for upgrade to V. 10 with about 120 users (on-premise). Currently running on a 2017 SQL. With it reaching EOL, customer is considering SQL 2022 (Standard) Considering lisensing per core. What are the mimimum/suggested # of cores that should be considered ?   regards      

Hi, We are working from a webpanel on the SuperOffice logo, and we need to open the dialog window to create a new appointment with pre-filled data. We can open up specific appointments just fine with: SuperOffice.ClientCrossMessaging.executeSoProtocol('appointment.main[refresh=false]?appointment_id='+id);   But, when running the following code, the Sale is not populated (but, it works when we are actually standing on the sale in the gui) SuperOffice.ClientCrossMessaging.executeSoProtocol('appointment.main[new=true]?appointment_id=0&sale_id=12345'); How can this be achived? Regards Pär Pettersson