Salient points in extension usage

Question: In the extension, I have added a new attribute (Txtl_Attribute1) to an object existing in the main configuration (catalog Products).

Afterwards, when I want to show the newly added attribute on the object’s item form, first I have to take all of the form’s attributes to the extension, which in turn takes all of the object’s attributes to the extension too. This is not acceptable since it creates too many dependencies (tens or hundreds of dependencies – all of the attributes of the object- when I only intend to have one – the Txtl_Attribute1 attribute) between the main configuration and the extension.

Is there a solution to this phenomena?

Answer: Yes, the solution is adding the “form attribute”, “form item” and “form item events” (if needed) corresponding to your object attribute which was added in the extension (Txtl_Attribute1) via programming.

Question: I have an extension attached to main configuration such as 1C:Drive, in this extension I develop the custom functionality of my vertical solution. However, other then developing this one and common for all of my client companies vertical solution, I also want to develop custom functionality per each one of my client companies. In such case, I cannot take the objects or modules which have been created in the higher level vertical solution extension to the lower level per client company extension for further development. This makes me lose time during updates, when my vertical solution gets updated. Is there a solution to this?

Answer: Currently, the extensions functionality does not allow to take an attribute which was created in an extension to another extension. So, there is no direct solution. However, by having as less as possible connections between the main configuration and the extensions (for example using the method which was mentioned in the previous question), you generally make your life that much easier during updates.