AUTOSAR types mapping in code generation

Hello,

I'm developing an AUTOSAR model following this process:

1. Importing the model from third party .arxml file
2. Applying modification to the model in Simulink
3. Generating C code from Simulink

Inside the .arxml from wich I import the model I see the following lines:

<SHORT-NAME>TypeMapping_General</SHORT-NAME>

<DATA-TYPE-MAPS>

.....

<DATA-TYPE-MAP>

<APPLICATION-DATA-TYPE-REF DEST="APPLICATION-PRIMITIVE-DATA- TYPE">/DataTypes/AdtLowPowerVoting</APPLICATION-DATA-TYPE-REF>

<IMPLEMENTATION-DATA-TYPE-REF DEST="IMPLEMENTATION-DATA-TYPE">/DataTypes/IdtLowPowerVoting</IMPLEMENTATION-DATA-TYPE-REF>

</DATA-TYPE-MAP>

......

So what I expected to happen inside generated .c/.h files was that all the input/output ports defined inside the model that were declared using application data type "AdtLowPowerVoting" were replaced inside source C code with implementation data type "IdtLowPowerVoting", but this does not happen, in fact inside generated code I find a lot of AdtLowPowerVoting variables declaration (and what I've just described happens for all the Adt/Idt pairs declared in DATA-TYPE-MAP in .arxml file). Does anyone know how to let Idt data type to replace Adt type inside generated code? Which properties should I check? Thanks in advance for any help,

Francesco