Notice: Urgent Information for SuperOffice Onsite 10.2.9 WCF API Users

So what exactly triggers this in bug in the API? changing a combination of fields at once? changing the description containing specific text fragments?

Hi!
Will this also affect the traditional calendar syncronizer?
Version History - Exchange Online Synchronizer – InfoBridge


I guess it is not fixed yet since the DL link i still withdrawn?
SuperOffice Onsite
Is the plan still to release a new version this week?

//Anders

As far as we know it's a backwards compatibility issue when connecting to an Onsite SuperOffice 10.2.9 Environment in Remote WCF Mode using a Newer WCF Proxy Package, the Nebula Synchronizer requires the newer proxy version due to new features in superoffice online (online is never affected!).

Any software using the above combination will have this issue, so be careful with custom solutions etc, afaik local mode is not an issue.

The onsite Exchange Online Synchronizer is not affected by this.

Technically what can be observed is that just updating an existing appointment empties existing properties in the appointment row upon save.

Thanks for the reply an clarification.

So if using nuget package for 10.2.9 in custom apps - That should be safe? 

When can we expect a corrected version and possibillity to download 10.2.9 again under downloads?
Will there also be new nuget packages for 10.2.9 or are they not affected?

Hi @Carlo and @Anders!

We have looked into this and concluded that onsite intergrations should use the same proxies versions as the target customer netserver web services. 

If R&D was to issue an updated nuget package, for 10.2.9.patch, then it's possible that some developers might see that and attempt to use the new 10.2.9.patch towards their onsite customers 10.2.9.x installation, and there it would fail because of yet-another-incompatability (related to WCF SOAP serialization).

We have determined that issuing a fix for this specific case could/would only cause more damage. 

SuperOffice has a fairly good track record with ensuring backwards compatibility. However, sometimes, new features require changes to entity carriers that, in the SOAP proxies, cause problems. This case would not be an issue in the [preferred] SuperOffice.WebApi package instead.

Remember, SOAP (and proxy client) is scheduled for END OF LIFE in the future.

We are striving to achieve strict sematic versioning from version 11. It is my hope that we will be able to follow that industry standard, and use our versioning strategy to increase confidence and maintain integrity of our API's for all of our development community. 

Best regards.

Ok, thanks Tony.
My mainproblem is now that I do not know if I can use the "with drawn" 10.2.9 (That I have downloaded in a customer TEST environment) for installation in a PROD environment? 
I can not see any issues in TEST (not all integrations like eMarketeer via separate NetServer and IB classic sync can be tested there) 
Do we have a new estimted relese date for 10.2.9 patched version and the upcoming 10.3.3 ?

Just a comment regarding this: "We have looked into this and concluded that onsite intergrations should use the same proxies versions as the target customer netserver web services. "

We have apps that work against both online and onsite installations. Currently the app is using older NuGet packages, and relies on the /Services86, /Services88 etc functionality for cross-version compatibility. So for us it's not really an option to use the same NuGet version as the version the customer has installed, since there is one installation of the app against many customers.

Our gameplan will most likely be to remain on older NuGet version until we can prioritize switching from SOAP to REST webservices.

Update: 

We are still investigating all options.

Currently investigating whether is it feasable to revert to 10.2.9 compatibility (last onsite release). However, that would mean that anyone using SuperOffice.NetServer.Services proxies towards online, which in SOD is currently 10.3.3, the versions released between those versions would most likely experiencing the same issue.

This doesn't seems like a easy road forward either way....

To be continued.

In light of Carlo's compatibility chart, it is 10.2.9 onsite that seems to be the bad egg (technical term):

So would it not be the best solution to release 10.3.3 (the next onsite release March 20th) instead of publishing both 10.2.9.x and 10.3.3, and advise all to upgrade customers to 10.3.3 instead of a 10.2.9 patch (which will be need to be upgraded eventually anyway)?

~Messenger

Hi, Yeah I think I agree on just skip further 10.2.9 version and focus on 10.3.3 release to get that out in time instead.

Hi, I guess the final decision was to not reenable 10.2.9. for download. And that we instead wait for 10.3.3 as now stated in the Relese-details of 10.2.9 (under current version)

SuperOffice Onsite

Best regards

In release note for 10.3.3, I do not see a reference to id 53654

Is this included but perhaps not documented, or, am I missing something.

Thanks for pointing this out Eirik - fix for bug 53654 was connected to release 10.2.9. It is now updated to 10.3.3:

I installed the 10.3.3 at a customer on Monday, but I cant get the TrayApp to work.

For details about the error see this post

https://community.superoffice.com/en/technical/forums/product-forums/crm-web-application/tray-app-problems-in-superoffice-10.3.3-onsite