Desktop version

Main > Knowledge Base > Developer resources > Development recommendations > 1C:Enterprise script > Specifics of reusing return values > Developer resources > Development recommendations > 1C:Enterprise script > Specifics of reusing return values > Developer resources > Development recommendations > 1C:Enterprise script > Specifics of reusing return values

Specifics of reusing return values

This article applies to common modules that have Server and Server call properties set to True and the Reuse return values property set to During session.

When export methods declared in the module are called from the client application, return values are cached both on the client and on the server.

During the call, the platform searches the client cache for the return value.

This can introduce data inaccuracies in scenarios where cached objects are changed by the client script. An object is changed in the client cache but it is not changed in the server cache. If the object in the client cache becomes obsolete, it is retrieved from the server, possibly from the server cache instead of executing the module body.

During configuration development, do not count on automatic updates of cached objects. Use the RefreshReusableValues method for forced cache updates.

If you decide to change certain objects in caches, use one of the following methods to avoid inaccuracies:

Next page: Storing values in object and form module variables




© 1C LLC. All rights reserved
1C Company respects the privacy of our customers and visitors
to our Web-site.