Cross HDI Container Access With CAP Localized Entities

[alpyesilgul0]

Hello,

In my project we are using cross hdi container and there is a table which is serving as a value help like this : 

.persistence.exists
entity ELEMENT_TYPES {
        key ELEMENT_TYPE_ID : String(36)   @title: 'ELEMENT_TYPE_ID';
        key LANGUAGE              : String(2)    @title: 'LANGUAGE';
            DESCRIPTION           : String(1000) @title: 'DESCRIPTION';
            MAIN_ELEMENT          : String(30)   @title: 'MAIN_ELEMENT';
            CODE                  : String(4)    @title: 'CODE';
            master            : Association to many MASTER
                                on master.ELEMENT_TYPE_ID = ELEMENT_TYPE_ID;
            transactional     : Association to many TRANSACTIONAL
                      on transactional.ELEMENT_TYPE_ID = ELEMENT_TYPE_ID;
}

I would like to get rid of LANGUAGE column and use this approach : Localized Data | capire (cloud.sap)

When I deployed the changes ( deleting LANGUAGE column and adding localize ) I got an error for every associated entity and their sub-entities : 

Error: The file requires "db://LOCALIZED_..." which is not provided by any file

I saw the nested localized data section on the webpage but I couldn't be sure what should I do. Do I really have to create all those tables/views or is there any other workaround for this scenario ?

[simon_oswald]

Hello,

It is hard to be certain without having the full model, error logs etc., but if you are not using @ash_G/cds-compiler@5 yet, it is worth giving that a try.
Behavior regarding localized + @CDS.persistence.exists was changed there, maybe this helps in your case.

Best Regards, Simon