MscrmTools

Hi Marcelo, Can you confirm the update did succeed and you are using version 1.2024.9.69?

Can you precise which kind of authentication method you are using? It seems to me that it occurs only with Microsoft Login Control method

This is the most complicated for me since I don't handle how it works, how it caches credentials, etc. As soon as you open Microsoft Login Control, my code is...

Yes, the version of Microsoft control changed. But as far as I can tell, nothing in my code has changed that could lead to this behavior

This is a known issue but as said @rappen it's not reproductible on purpose and I really don't know how to fix it

Hi, It's true timeout configuration is not exposed when using Microsoft Login Control. And there seems a bug prevents from storing changed timeout value. I will work on this but...

Can you confirm what kind of connection you are using? Were they created using Microsoft Login Control or not?

Thank you Jonas. I already identified this problem and fixed it in code. It seems chrome changed the way to store some profile information (name included).

Did you try to configure proxy settings?

Thanks @GerritRega That would mean that I missed something when configuring proxy... I will double check this and find why it's not saving changes to the XML file