You can't use those custom properties with a component profile because component profiles cannot reference custom properties. You're probably going about this in the wrong way to begin with. Rather than setting disk-level custom properties, you should be creating and leveraging storage reservation policies. Read the docs for how those work.

---------------------------------------------------------------------------------------------------------

Was it helpful? Let us know by completing this short survey here.

To use both together you'll need to apply some backend logic that associates a storage reservation policy with the value of the custom property that represents the image. You can manually do this in vRO with custom code, but I don't do that and instead use the Property Toolkit to apply that dynamically.