[RESPDAM-45] Missing createdDate brings AssetResolving to fail Created: 10/Jun/21  Updated: 19/Oct/21  Resolved: 19/Oct/21

Status: Closed
Project: DAM Focal
Component/s: None
Affects Version/s: 2.0.6
Fix Version/s: None

Type: Bug Priority: Critical
Reporter: Pierre Sandrin Assignee: Adrien Manzoni
Resolution: Fixed Votes: 0
Labels: quickwin
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

6.2.8 DX-Core


Attachments: PNG File Bildschirmfoto 2021-06-10 um 14.05.19.png     PNG File Bildschirmfoto 2021-06-10 um 14.11.06.png     PNG File Bildschirmfoto 2021-06-10 um 14.14.50.png    
Issue Links:
relation
is related to MGNLDAM-969 Uploading Asset via Assets-App does n... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

Steps to reproduce

  1. Add an Asset (The createdDate ist not set due to bug MGNLDAM-969)
  2. Link it in a Component
  3. Call the delivery Endpoint with an AssetFocalReferenceResolver

.. Logs, screenshots, gifs...

Expected results

The Json should be outputted with the resolved the Asset variations

Actual results

  • JSON is corrupt
  • 500 Server Error is returned

Workaround

Use the "old" Assets App

Development notes

AssetFocalWriter.java:133

asset.getCreated() should be checked if it is null.



 Comments   
Comment by Pierre Sandrin [ 10/Jun/21 ]

Related to MGNLDAM-969

Comment by Adrien Manzoni [ 19/Oct/21 ]

Fixed in DX core

Generated at Mon Feb 12 00:41:59 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.