You are not logged in.
Hello,
I have defined a metadata key (metadataTest) in a base report and setting to 'base value' as value.
I have defined the same key (metadataTest) in a variant of the mentioned base report and I have set metadata in definition as 'variant value'.
Query is like thois:
select ${_RS_METADATA_SUPER_metadataTest} C_BASE,
${_RS_METADATA_metadataTest} C_VARIANT
from dual where rownum=1
Now, I run the VARIANT and I get this
C_BASE C_VARIANT
-------------------------
base_value base_value
As far as I have understood, second attribute should output the data stored in VARIANT i.e. 'variant value' but it is showing the BASE data value.
Could you please assist ?
Regards
Alfredo
PS: Using 3.0.3 CE
Offline
Hi Alfredo,
I don't quite get what you are trying to do. Why did you set the same key for two different reports (the base report and the variant)? This seems not correct. Each report ( and variant ) should have a unique key defined. Or what do you mean with "metadata key"? Could you post some screenshots ?
Regards,
Eduardo
Offline
Hello Eduardo,
thanks a lot for your answer.
Please have a look to https://drive.google.com/file/d/1gO3cgs … sp=sharing
Regards
Alfredo
Offline
Hi Alfredo,
we are looking into this in this ticket: RS-2918
Regards,
Eduardo
Offline
Thanks a lot Eduardo
Offline
Hi Alfredo,
which patch are you using ? Please post the exact reportserver version.
Regards,
Eduardo
Offline
For this, please post the complete "rsversion.properties" file.
Offline
Hi Alfredo,
I suppose you use patch 6001, can you please confirm?
* In patch 6001 you have the behavior you observe while executing the base report: you get NULL for your _RS_METADATA_md_report_variant column.
* In patch 6002 you should get an error while executing the base report: "Cannot find property _RS_METADATA_md_report_variant". This happens since in this version we throw an error if a property is not being found (a more strict behavior).
I corrected the bug you sent in this thread. The problem was that the variant only contained _RS_METADATA_md_report_base. That's why you are getting a NULL in _RS_METADATA_md_report_variant when executing the variant.
This will be included into the next patch: 6003.
So in patch 6003 the behavior will be:
* If you execute the base report, you get an error: "Cannot find property _RS_METADATA_md_report_variant". This is correct, since in the base report you don't have this property. You can of course add to the base report md_report_variant with an empty value. Then you will not get this error.
* If you execute the variant, you will get both columns: _RS_METADATA_md_report_base and _RS_METADATA_md_report_variant.
Regards,
Eduardo
Offline
Hi Eduardo,
here you are
#
#Wed Oct 25 16:11:03 CEST 2017
version=RS3.0.3-6000
schemaversion=RS3.0-9
buildDate=1508940663593-2017-10-25-16-10-52
About 6003 it is ok thanks.
I will be expectant for that release ...
Kind regards
Alfredo
Offline
Hi Alfredo,
ok, the behavior in 6000 and 6001 is the same with respect to this, so it makes sense.
Regards,
Eduardo
Offline
Eduardo one more question please.
If I would like to install the release 6002 , should run a complete installation donwloading from https://reportserver.net/en/download/, or would it enough just donwloading reportserver.jar and replacing file in lib folder ?
Thanks
Alfredo
Offline
Hi Alfredo,
you can perform an upgrade analogously to the upgrade to 3.0.3 described here: https://reportserver.net/en/tutorials/upgrade-303/
Regards,
Eduardo
Offline