We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.
For technical issues or bugs please head to Support or our Developer Community. You can assign up to 10 votes in total. Thank you for your feedback.
Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.
Yes, an example here would be for a custom implementation we had for 360 images that aren't from SIRV. We previously had an implementation within commerce to have a custom property for how many rows/columns existed for the rotational image, and the viewer handled the images automatically on the front-end. Within commerce it was easy, we just had a custom property. When the customer migrated to PIM, it made it much more difficult to implement b/c there wasn't an easy way to pass this extra metadata back over to commerce from PIM unless it was an attribute on a product. A way to pass metadata on an asset (image/document) would have been helpful. We were limitted to just the couple fields that are mapped over (description, alt text, image url)
Thanks for the recommendation. Do you have a use case in mind where you would need a custom property on an asset?