[EXTDAM-417] S3 asset lastModified Property Returning Wrong Value Created: 25/Jan/24 Updated: 31/Jan/24 |
|
| Status: | Open |
| Project: | External DAMs |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Normal |
| Reporter: | Julian Nodarse | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| 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: | |||||
| Team: | |||||
| Description |
|
The Assets app contains the correct value in the last modified date column. However, the timestamp returned by the asset through the API is the current date (not the last modified date). The last modified date is only returned wrongly when called from the asset object. Example from the linked HELPDESK ticket:
[#assign imageAsset = damfn.getAsset(p_imgObj) /]
[#assign modifiedDate = imageAsset.lastModified?string["yyyy-MM-dd_HHmmss"] /]
|
| Comments |
| Comment by Manuel Sanchez [ 30/Jan/24 ] |
|
Hi, Do you have an ETA for this?
Thanks! |