@Salesforce Mojo, Thank you nice Video. I have a question: When I create an attribute set, I think we can select picklist or checkbox field from product2 object as well not only from the Product attribute, Am I right? And If I am right, in your opinion when should we put the field in product attribute and when we should put in in Product2?
Hey! I might not be understanding the question but you need to create a new field on the attribute setup object, it can't be on the product. These fields are specially used to create the variation relationship. help.salesforce.com/s/articleView?id=sf.comm_var_att_intro.htm&type=5
I'd love a video about how CPQ integrates with b2b commerce. Also I'd be curious to hear your thoughts on different industries that might use commerce differently, like SaaS companies.
That’s funny, I was actually just doing some CPQ to commerce connector work the other day. I’ll add that to the list, likely after the next one I have planned! The industries one is a good thought, I’m trying to think how I could articulate all of that into a single video. 😅
i remember there is a limitation that does not allow to associate existing products to a new Variation Parent via the UI. Has to be done from backend with data loads... is that still the case?
As far as I’m aware that is still the case! I can’t wait for them to fix that. Might actually be a good community component that one of us could build now that I think about it..
We have a little issue. We have been using shopify syncing to salesforce. The problem is all of our products were created as simple products as we didn't have the option prior to SF Commerce. You said it can be done but on the back end. What steps do we need to take.
I don’t have the exact steps mapped out but it invokes going into work bench and updating the records and values on fields to map to the attribute sets created.
Great video as always
Thanks!
@salesforcemojo how in possible to create parent product in apex class or via api ?
@Salesforce Mojo, Thank you nice Video. I have a question: When I create an attribute set, I think we can select picklist or checkbox field from product2 object as well not only from the Product attribute, Am I right?
And If I am right, in your opinion when should we put the field in product attribute and when we should put in in Product2?
Hey! I might not be understanding the question but you need to create a new field on the attribute setup object, it can't be on the product. These fields are specially used to create the variation relationship.
help.salesforce.com/s/articleView?id=sf.comm_var_att_intro.htm&type=5
I'd love a video about how CPQ integrates with b2b commerce.
Also I'd be curious to hear your thoughts on different industries that might use commerce differently, like SaaS companies.
That’s funny, I was actually just doing some CPQ to commerce connector work the other day. I’ll add that to the list, likely after the next one I have planned!
The industries one is a good thought, I’m trying to think how I could articulate all of that into a single video. 😅
@@salesforcemojo awesome, looking forward to it
@@salesforcemojo Excellent series... Can you PLEASE make CPQ connector video? thanks
@@salesforcemojo SaaS, as well pharmaceutical and industrial equipment will be nice.
Awesome 🎉
Thank you! Glad you enjoyed!
i remember there is a limitation that does not allow to associate existing products to a new Variation Parent via the UI. Has to be done from backend with data loads... is that still the case?
As far as I’m aware that is still the case! I can’t wait for them to fix that. Might actually be a good community component that one of us could build now that I think about it..
We have a little issue. We have been using shopify syncing to salesforce. The problem is all of our products were created as simple products as we didn't have the option prior to SF Commerce. You said it can be done but on the back end. What steps do we need to take.
I don’t have the exact steps mapped out but it invokes going into work bench and updating the records and values on fields to map to the attribute sets created.