Summarized answers/solutions:Right format of languages in CIFX file is this: <LANGUAGES> <LANGUAGE> <LANGUAGE_CODE>en</LANGUAGE_CODE> <CLIENT>true</CLIENT> </LANGUAGE> <LANGUAGE> <LANGUAGE_CODE>cs</LANGUAGE_CODE> <CLIENT>true</CLIENT> </LANGUAGE> <LANGUAGE> <LANGUAGE_CODE>de</LANGUAGE_CODE> <CLIENT>false</CLIENT> </LANGUAGE></LANGUAGES> For APP10 languages should be also in Order/Config File: [languages]encsde[components]wrksch 8.0.0;12... It looks like it doesn’t matter on this configurations CIFX (and maybe also Order/Config file) should contains only one record per “Module Name”. So never: <!-- Bad! Do not use this way --><MODULE> <NAME>FIXASS</NAME> <VERSION>10.0.0</VERSION> <MARKET>GET</MARKET> <VERTICAL>None</VERTICAL> <CPS>12</CPS></MO
Hi @jasahu,Finally, I think I found only way to solve this situation like this:I created Merged archive folder, that contains Core, GET and MEE.Core subfolder contains only core files, GET subfolder contains GET files on top of Core files and MEE subfolder contains MEE files on top of GET files on top of Core files.I also created RRC file that contains all three markets.In CIFX I then use only one record for module with market I need.For Example:<MODULE> <NAME>ACCRUL</NAME> <VERSION>10.0.0</VERSION> <MARKET>GET</MARKET> <VERTICAL>None</VERTICAL> <CPS>11</CPS></MODULE>We are currently testing it on few environments, but I think it’s only way.Maybe there can be problem if you want use MEE without GET, but now only module where are all three markets is documentation.BRFilip
Hi @hamalk ,thanks for response.I'm very glad to hear about this DS feature. Yeah, I know how deploy.ini works.But our programmers common mistakes are:missing $ELSE invalid $ELSE not editing deploy.ini to add DYNAMIC dependencyAnd we are facing problems with GET modules - of some reason SD while building deliver fetch deploy.ini from Archive of Core and not from GET.It must be related to this question: Right CIFX format | IFS CommunityOnly working solution for this is add deploy.ini to harvest - but it is not good solution for applying Bugs and Updates.So we adding deploy.ini from GET to ManualInsertFiles folder before every delivery, but sometimes we mistakenly replace also deploy.ini from harvest, where new dynamic modules are registered.Most of this added dynamic dependencies are nonsense, for example: INVOIC, PAYLED, ENTERPAll our customers have these modules, so will be easier to do not use Conditional Compilation for them to avoid mistakes.So I want to create rule, that will said
Hi @InfFilipV, Regarding point #3: We have the same problem and it is quite annoying. Have you managed to find a solution? regards Janos Hi @jasahu,unfortunately no.But, we had this issue also in delivery process, sometimes Ext was not loaded and dynamic dependency modules was not loaded very often.Solution Developer before delivery checkout deploy.ini from harvest, and because there is problem with not downloading GET files, it ignore them and use Core one from Archive.So we check-in GET version of deploy.ini into _STD package and it helps (or we manually adding this deploy.ini files as ManualInsertFile to the delivery - and before build changing build from fresh to up-to-date). This could help also in deploy on local machine.I spend last year on previous versions where we does not using GET, so I did not try solve this issue.Only my actual idea without try:Maybe checkout of GET deploy.ini into workfolder and making file writable (to avoid rewrite by SD) will help. Filip
And to add unistr() you can use regexp replace SEARCH: '[^']*\\[^']*' REPLACE: UNISTR\($0\)
Hi, you should use UNISTR function. SELECT UNISTR('abc\00e5\00f1\00f6') FROM DUAL;UNISTR------abcåñö To convert you can use function ASCISTR SELECT ASCIISTR('abcåñö') FROM DUAL;ASCISTR-------abc\00e5\00f1\00f6 To convert whole file you can use something like this: DECLARE str_ varchar2(32000) := q'[select 'ěščřžýáíé' from dual]';BEGIN dbms_output.put_line(asciistr(str_));END;
@ChanakaAmarasekara : Thanks, I know what I must do while install. I hoped there is some standard practice to achieve right folder structure and avoid forgot manually copying of layouts. For example Delivery Builder could automaticaly copy all *rpt from <module>\server\layout to ManuallInstallation folder.
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.