amplience / dc-visualization-sdk

For supercharging your Dynamic Content visualizations
https://amplience.github.io/dc-visualization-sdk/
Apache License 2.0
6 stars 1 forks source link

Realtime visualization displays only one item from content array when in a slot content. #23

Closed tk-olari closed 3 years ago

tk-olari commented 3 years ago

Description

Realtime visualization displays only one item from content array when in a slot content, it's clearly an issue related to dc-visualization-sdk, when we do popup visualization, we are fetching the data using HTTP and all of the data is present(all items from content array are rendered).

Note that in both scenarios the content is Published (latest version).

This issue creates impediments for our QA team and client's Content team.

In case that something is not clear, I can share more details in slack as I can't post in public any screenshots or direct links to demo the issue.

Steps to Reproduce

  1. Create a content type with a property which is of type array.
  2. Add some content to the array, should be more than one.
  3. Go to visualization and observe that all items of the content array are rendered.
  4. Create a content slot and use the created content type in it.
  5. Observe when in visualization of the content slot that only one item from content array is rendered.

The following visualization can be used:

https://delivery-preview.visualizations.content.amplience.net/?realtime=true&id={{content.sys.id}}&vse={{vse.domain}}&hub={{hub.name}}&locale={{locales}}

Expected Results

All of the items of a content array should be rendered in visualization for both content & slot.

Actual Results

When in visualization of the content, all items of a content array are rendered. When in visualization of the slot, only one item from the content is rendered.

Affected browsers/environments

Does not depend on the browser.

Versions

github-actions[bot] commented 3 years ago

Welcome to Amplience community! Thanks so much for creating your first issue ✔️

pixelscript commented 3 years ago

Hi @tk-olari. We have looked into your issue and determined that it is a bug that exists in our Dynamic Content platform, not this repository. As a result I'm going to close this issue, however we intend to release a fix the issue in our platform soon.

Thanks,

Chris

pixelscript commented 3 years ago

FYI @tk-olari this fix went out today. Let me know if you see the issue anymore.

All the best,

Chris

tk-olari commented 3 years ago

@pixelscript We did a quick check and the issue seems gone! Thank you!