This can be achieved in DOM with the code like:

const textEl = document.getElementsByClassName("crt-input-control")[0].childNodes[0]
textEl.addEventListener('focus', (event) => {
    event.stopPropagation();
    console.log('focused');
})

But you need to study the page content to properly process the NodeList and add the focus event to the needed input.

.

Oleg Drobina,

That is the problem, that I can't find out to which attribute the input belongs 

Davit Gharagebakyan,

how about using textEl.ariaLabel to get the label (caption) for the input and use it to identify the needed element?

Oleg Drobina,

in my case area label is BIrthplace (for example). I don't have such a text in context. (only in very deep nested objects =>

 $context.viewModelGenerator.injector._lView[3][3][3][3][3][3][3][3][3][3][3][3][3][3][3][3][3][3][3][3][3][3][3][3][3][3][8]._faviconService._sysSettingsService.httpClient.handler.injector.parent.parent.records[11][1].value._modules[0].instance._crtInjectionContextService._injectionContextsMap[0][1]._injector.records[3][1].value._crtRouter._location.
window.handlerChain._handlersCache[18][1][0][1]._next._injector.records[3][1].value._routerOutletHistory._items[8].view.pageRef.instance.schemaState.models[0]._dataSourceFactory._dataSourceRepository._repository[2][1]._queryExecutor._httpClient.handler.injector.records[1291][1].value.cachedInjectors[0][1].records[297][1].value._dragDropRegistry._drop
Instances[0].data._changeDetectorRef._lView[3][3][3][3][3][3][3][3][3][3][3][3][3][3][3][3][3][3][3][3][3][3][3][3][3][3][3][3][3][3][3][3][3][3][3][8]._cacheService._componentRefCache[0][0].instance.refs.root.changeDetectorRef._cdRefInjectingView[19].queries[0].queryList._results[0].changeDetectorRef._lView[4][4][4][8][0]._lView[13][9][0][3][3][3][3
][3][3][3][3][4][8][0]._lView[4][7][0]._results[0]._closestTab._closestTabGroup._tabs._results[0]._viewContainerRef._lContainer[4][9][0][13][8][0]._lView[13][8][0]._lView[19].queries[1].queryList._results[0]._rendered[0][0]._declarationLView[19].queries[3].queryList._results[0].changeDetectorRef._lView[4][4][4][4][4][4][4][8][0]._lView[13][4][4][8][0]._lView[30]
) 

If it's a compilation error, maybe there is more details in the Compilation errors? In the lookups section, add the "Compilation errors" object to view the contents.

Ryan

Hello Kevin

In my case, the problem was caused by a duplicate lookup object: deleting the duplicate solved the problem.

The new equivalent of a lookup is "Dropdown"

Ryan

Hello,

If you are developing in order to later transfer these changes to a production website (or any other website), it is essential to transfer these elements from the Custom package, as you have different bindings and data, as well as changes made to the objects. If you do not transfer them, the integrity of the development will be compromised, and the package is unlikely to be successfully installed on the target website.

Also, please note that the package must include all the necessary dependencies for these elements to be transferred. If, at the moment you want to move an element, you are missing a dependency, for example, the website will display a message indicating what is specifically missing.

Additionally, please familiarize yourself with the documentation:

Packages basics

Delivery in Creatio IDE

Move the functionality between packages

Kalymbet Anastasia,

I understood

I just have a further question.

If, I move all the elements from the Custom Package to my A package on the Development website. Then, I install that package on the Production website. The Production already had a Custom Package with all the same elements as the Development website.

Is there any possible error when I install my A Package on the Production site?

Bao Phan,

If they are the same elements with the same UId and name, then yes, there may be a conflict during installation.

Kalymbet Anastasia,

So if I create another package (B package) and move all elements from Custom Package to the B package on Production Site.

Then, I continue to develop A Package on the Development site and install it later on the Production Site

Is it possible doing it? Any conflict or error may happen?