A custom attribute called subType is created in the attributes page with the scope being only product. Default value is already been set. String type and Inherit is enabled. Can this attribute be used in the Anatomy of a project so that during publishing, the folder structure would be something like this:
{root[work]}/{project[code]}/{hierarchy}/{folder[name]}/publish/{product[type]}/{product[name]}</{product[subType]}>/{@version}
I’m afraid we don’t support that.
I also don’t understand when/where it should be used? Attributes can be set on existing entities (products), during publishing is product being created, without existing entity there is no attribute to be available.
So, I would say the question is: What is intended usage and reason behind?
Ok. In that case, can you please suggest a way to manipulate the folder structure so that we can give any custom key in the Anatomy preset of a project. This custom key can be given by us while creating a product and the path should be resolved including this key as well.
Is there any other way?
@iLLiCiT
You are describing what you think you need instead of describing your use case. It will mean we’ll basically be telling you: “what you want to do makes no sense.” like what @iLLiCiT mentioned above. Instead, we need the information about what is your production use case about what you actually need to do and why.
I will try to answer the questions one by one.
What is it that you need to store and where?
Take the product plate for example. I want to define if the client given plate is for BG or FG. These values would be used to define the sub type of the product. Granted, the variant or product name can be used, we internally use it to map another field of ours called namespace.
Why do you need to customize the path with a subtype?
Currently we are using the sub type for customizing the along with the product type in our company.
What defines that subtype?
Already mentioned for the first question.
Why is product type alone lacking your use case?
It is not about lacking anything. Our DB is structured with a field called sub type which is also used create the folder structure. So if we could somehow replicate the same in AYON, we will have no problem integrating AYON for our use.
@BigRoy
On that note, at current, this does feel out of scope for our backlog for a community request - it seems rather specific.
Nothing is stopping you from technically adjusting the formatting logic to allow custom data to be put into it. Most likely needed in the Integrator and making sure it’s stored with the published representation’s context too.
A starting point would looking around this area in the codebase. Hope that helps.
If needed we could help out. This is exactly the kind of requests we pick up for clients under active Ynput support.
Thank you for the guidance.
We will definitely try it out.
We have in backlog issue that is meant to solve similar issues (different approach). But it is not high priority.