BOster
Legendary Poster
Is there any way to categorize media objects not by content type but by user defined categories?
We use the Sales Order Header media attachments for a couple of different things:
1. delivery instructions
2. missed delivery notes (we also put order on MD hold)
3. general notes
4. ... etc.
Different reports may need to display different notes. For example delivery tickets may need to display delivery instructions but NOT missed delivery notes. Another report may need to display all the missed delivery notes but nothing else.
What we do today is VERY dependent on the user following instructions correctly. First text attachment is for delivery instructions, Missed Delivery instructions are after the first attachment and are named "MD1", "MD2", etc.
We could obviously create new custom GT structures for the different categories and then heavily modify SOE for user edits and to manage all this but this has obvious downsides.
What we really need is to simply use the GT4201A struct for all notes but have a more structured, validated way to categorize them. The ordinal position and naming convention thing I mentioned will work (i.e. have a prefix name for the attachment that categorizes it) but not optimal IMO.
Any ideas?
We use the Sales Order Header media attachments for a couple of different things:
1. delivery instructions
2. missed delivery notes (we also put order on MD hold)
3. general notes
4. ... etc.
Different reports may need to display different notes. For example delivery tickets may need to display delivery instructions but NOT missed delivery notes. Another report may need to display all the missed delivery notes but nothing else.
What we do today is VERY dependent on the user following instructions correctly. First text attachment is for delivery instructions, Missed Delivery instructions are after the first attachment and are named "MD1", "MD2", etc.
We could obviously create new custom GT structures for the different categories and then heavily modify SOE for user edits and to manage all this but this has obvious downsides.
What we really need is to simply use the GT4201A struct for all notes but have a more structured, validated way to categorize them. The ordinal position and naming convention thing I mentioned will work (i.e. have a prefix name for the attachment that categorizes it) but not optimal IMO.
Any ideas?