Environment: CMS 4.3.1 (self-hosted, Docker) · Xibo for Tizen v4 R409 · Samsung QM55C, firmware S-PTMLWWC-1120.8
Parameters set on a scheduled Data Connector event never become window parameters inside the connector on Tizen, even though the CMS delivers them correctly. According to the Data Connector Docs they should be “made available as window parameters inside the Data Connector.”
The CMS sends them: schedule XML captured from a player’s library:
<connector scheduleid="30" dataSetId="5"
dataParams="CardId%3D00nqV%26Key1%3DDEPARTMENT%2BROLLUP%26Oper1%3DEQUALS%26Value1%3DBAKERY"
js="dataSet_5.js" ... />
The Tizen player drops them: a diagnostic in onInit enumerates Object.keys(window) for CardId|Key\d|Oper\d|Value\d|dataSetId and displays the result on screen via xiboDC.setData. It renders DIAG dataSetId=5 only: dataSetId is injected, none of the dataParams keys exist. Player logs show the connector is delivered and started normally (DataConnectors: Add / iFrame loaded). The same params work in the CMS Test Params harness.
Reproduce: real-time DataSet + connector that enumerates window keys in onInit → schedule a Data Connector event with parameters to a Tizen R409 display → power-cycle. Only dataSetId appears. Reproduced after recreating the DataSet from scratch (ids 4 and 5) and full power cycles, so not a stale instance.
Is dataParams injection expected to work on Tizen R409?