New Update Question
I have a problem with the process I was previously using in my canvases. It looks like the "active" command under the "set property-Image-CanvasComposite-active" in the rules logic is no longer an option. I have been trying to figure out an alternative but haven't had any luck yet. The new node query option is also confusing me. There are a few ways I think I should use it but I can't figure out how to get any of the results I want.
Here are a few screenshots of my logic to show you where the problem is.
Quick links
Comments
7 comments
Hi Julia Kaiser -
The active property still exists on CanvasComposite operators, so I believe there may be another issue at play here.
Are you trying to control the 'active' property via attribute? If so, does that attribute still exist or has it been deleted or renamed?
If not, do those yellow warnings give you any insight onto what the issue may be?
As for the node queries, can you give me an example of a way you think you would like to use it? I'm happy to create a sample or chat through use cases.
Hi Will, thanks for the help!
When I hover over those yellow warnings it says "This property is no longer configurable" and then when I go to my new canvas and try to do the same setup, there is no "active" option under the set property rule. I have not deleted or renamed anything. The attribute I am using specifies what package the user has so for example, "renegade xrs" would swap out the correct logo source images and then turn on/off certain canvas composites when needed. Like if the user changed their selection to "mxz blizzard," those disabled layers would be active and layers 14 and 15 would be disabled instead. I can provide a link to a working product and the asset I'm currently working on if that would help. I also opened a case yesterday kind of going a little more in depth on the same stuff.
I see, thanks for the details. Unfortunately I am not able to replicate the issue so I think getting support from the case is the best path forward, would you mind providing me with the case number?
In the meantime, if you have an example of how you may like to use node queries I'd be happy to see if I can make an example.
Hmm, that is so weird! I attached a photo of the logic path without the "active" option so you can see what it looks like on my end.
And then the case number is 00006538. It is kind of hard to explain what all I have going on so here is a link to one of our product pages. If you choose one and go to "3D Virtual Customization" you can see the configurator in action and the results.
https://www.scsunlimited.com/collections/rev-gen5?filter.p.product_type=Ski-Doo+REV+Gen5+Trail&filter.v.price.gte=&filter.v.price.lte=
It's hard because each product is specific to a design so I'm having a hard time wrapping my head around how to simplify all the moving parts. But I think the simplest example would be the overlaminate material selection. The user has the ability to choose from 8 different overlaminates which I have been just making a material for each and swapping it out in the model asset rules. However, I feel like the better way would be to make 1 material per product design and then write a query for the different overlaminates?? I just get confused with having so many different and specific designs so is that too global?
I know I am not explaining well so if you need more clarification let me know!
Hi Julia, thanks for the additional context and for your patience while we were our for the holiday. I think there may be a conflict somewhere in the setup or perhaps a bug - there was activity on your case yesterday by our team, if you have not heard back yet someone will be in touch soon. In the meantime, please feel free to check back here if there is anything else I can do.
Hi William, I do have one more question for you - I found a workaround to not having the "active" option but I wanted to make sure that it won't cause issues in the future if I use it moving forward. Instead of disabling certain layers to later activate, I left the layers active and then in the rules logic I used the "source image" option under set properties and left the asset empty to "turn it of" if that makes sense.
Here are a couple more screenshots for context
If that is working and giving you the outcome you are looking for and you are not using any undocumented APIs or custom scripts I do not believe there will be an issue on the platform side. There is always a chance of someone setting up a conflicting rule but otherwise it seems okay to me. Hopefully when your case is resolved we can figure out why the active parameter is missing from your rules!
Please sign in to leave a comment.