Version | 2.128 and higerhigher |
|---|
What will change?
To have all fields writable in the Media Configuration we made improvements for our Media Configuration component which might have an impact on your custom logic and setup of the Media Configuration.
Why are we doing this?
This improvement will reduce the view state size.
Some Media Configuration features require fields to be writable to work properly. This applies for example for our Dynamic Pricing feature or our Creative Targeting feature.
The improvement will therefore not only make the features more usable but also help to avoid errors and incorrect data.This improvement will also reduce the configuration overhead, because the Admin does not need to care about having all fields defined in the tabs
What do you have to do?
Please test if your current custom setup of the Media Configuration is still working.
...
If you need to access hidden fields with your javascript you can add them to the feature setting and use the function:
| Code Block |
|---|
adv.getValue(<itemId>, <fieldname>); |
The Feature Setting can be set up like this. You can add all fields there where you would need to be able to access them although they are hidden:
Feature Setting Name | Feature Name | Value |
|---|---|---|
AdditionallyAvailableHiddenFields | ModifyCampaignItems | API names semicolon-separated, eg. |
If you need to access hidden fields with your javascript via DOM e.g. as a change handler there are two options you could perform in order to fix your custom javascript code:
Precondition: You know when a hidden field is being changed in your code.
You would not need the change handler anymore because you could directly trigger the logic based on the change after setting the values.You could make the fields visible in your Media Configuration by disabling the Tab Rules. This will help you to access the desired values.
When the logic to get the value from the desired hidden fields was executed you could hide it via javascript again.