the nextcloud_url is only stored in res.config.settings which is a transient model. So when the transient record is automatically canceled by Odoo from the database, the nextcloud_url value is lost. Proposal: add the nextcloud_url in res.company and refer to it as related field from res.config.settings.
The fields nextcloud_login and nextcloud_password are stored as config_parameter, but this way they are not multicompany compliant because config_parameter is global. Proposal: add nextcloud_login and nextcloud_password in res.company and refer to them as related field from res.config.settings.
Every time nextcloud_url, nextcloud_login and nextcloud_password are called by the user, they must be read from the actual company of the current user. In case of cron jobs, all the companies should be considered.
Looking at the definition of fields in
res.config.settings
:the
nextcloud_url
is only stored inres.config.settings
which is a transient model. So when the transient record is automatically canceled by Odoo from the database, thenextcloud_url
value is lost. Proposal: add thenextcloud_url
inres.company
and refer to it as related field fromres.config.settings
.The fields
nextcloud_login
andnextcloud_password
are stored as config_parameter, but this way they are not multicompany compliant because config_parameter is global. Proposal: addnextcloud_login
andnextcloud_password
inres.company
and refer to them as related field fromres.config.settings
.Every time
nextcloud_url
,nextcloud_login
andnextcloud_password
are called by the user, they must be read from the actual company of the current user. In case of cron jobs, all the companies should be considered.