wir haben einen Produktkatalog angelegt und in den Produkten auch immer schön das Feld "Product Type" gepflegt, um hinterher nach diesen Kategorien auswerten zu können. Leider finde ich das Feld in der Data source "Line Item" nicht und kann im Report auch nicht die Datenquelle "Product" dazuwählen.
bei mir funktioniert das – wenn ich ein Eigenschaftsfeld für das Objekt "Produkt" (Einstellungen > Eigenschaften) anlege, dann kann ich in einem benutzerdefinierten Bericht (Menü > Berichte > Berichte > Bericht erstellen) auch dieses Feld im Bericht verwenden.
Update: Ich habe gerade nochmal geschaut, die Standardeigenschaft für "Product type" ist tatsächlich nicht in Berichten verwendbar, warum ist mir auch nicht klar. Meine Empfehlung wäre hier, auf den HubSpot Support zuzugehen und nachzuhaken. Grundsätzlich müsste das Feld dort erscheinen, da auch benutzerdefinierte Felder im Bericht verwendet werden können.
Ein Workaround wäre, dass man ein benutzerdefiniertes Feld erstellt und dieses pflegt. Das erscheint dann in Berichten korrekt.
Viele Grüße!
Karsten Köhler HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer
Ok, so I have found a pretty detaild internal ticket on product type property which might explain this. Please be assured that at least you are not the only one experiencing this, and I also cannot use product type in report on my own portal. Just to clarify that Products and Line items are not really the same thing either structure wise. Line items are "sourced" from the Products, but all in all, in a report we can report on Line Items and not Product properties. The question as you pointed out is more : why the product property thus did not transfer to the line items. hence my research here.
Here is the ticket that I have found internally :
It looks like based on this article, this property [Product type] is a HubSpot default property that is used to "categorize your product library. This field is especially crucial to ensure your products sync correctly with other apps, such as Netsuite." As a result this product property does not appear in line items unlike other custom created product properties like [Sales account] (see screenshot) and cannot be reported on.
In this case, in order to have a reportable [Product type] property:
A new custom [Product type] product property needs to be created
Now when creating new line items, the new custom [Product type] product property set for a product will be copied over to the line item.
However, the above only applies to new line items moving forward and I understand that you have existing line items that you wish to report on. I've checked in on this internally and can confirm that it isn't possible to push an update to the new custom [Product type] property for all existing line items once the Product they were created from is updated from the above method. This is because when a product is added to a deal, it becomes a totally separate line item object that can be updated individually from the source product object and from its 'cousin' line items.
The team has shared that in order to update the existing line items there are only 2 possible approaches.
1) Update the new custom [Product type] property for all existing line items manually
2) Update in batch via API
Using API will allow for bulk actions more easily but it does require someone who knows how to run endpoints
We can identify which product object the line item was created from by looking at a hidden line item property called hs_product_id. Identify the product ID from the product library by selecting the relevant product(s) > Export > Check the export file for the object ID
With the Product object ID, use the POST/crm/v3/objects/line_items/search to search through all line items to identify line items that originated from the product
After getting a list of line item IDs, you can then use the POST/crm/v3/objects/line_items/batch/update request to update the required property value of these line items in bulk
This would need to be repeated for each product in the product library
und nochmal vielen Dank. Ich werde den Support kontaktieren und überdie Reaktion berichten. Sollte mir das nicht weiterhelfen, werde ich wohl auf den Workaround mit dem benutzerdefinierten Feld ausweichen müssen.
Ok, so I have found a pretty detaild internal ticket on product type property which might explain this. Please be assured that at least you are not the only one experiencing this, and I also cannot use product type in report on my own portal. Just to clarify that Products and Line items are not really the same thing either structure wise. Line items are "sourced" from the Products, but all in all, in a report we can report on Line Items and not Product properties. The question as you pointed out is more : why the product property thus did not transfer to the line items. hence my research here.
Here is the ticket that I have found internally :
It looks like based on this article, this property [Product type] is a HubSpot default property that is used to "categorize your product library. This field is especially crucial to ensure your products sync correctly with other apps, such as Netsuite." As a result this product property does not appear in line items unlike other custom created product properties like [Sales account] (see screenshot) and cannot be reported on.
In this case, in order to have a reportable [Product type] property:
A new custom [Product type] product property needs to be created
Now when creating new line items, the new custom [Product type] product property set for a product will be copied over to the line item.
However, the above only applies to new line items moving forward and I understand that you have existing line items that you wish to report on. I've checked in on this internally and can confirm that it isn't possible to push an update to the new custom [Product type] property for all existing line items once the Product they were created from is updated from the above method. This is because when a product is added to a deal, it becomes a totally separate line item object that can be updated individually from the source product object and from its 'cousin' line items.
The team has shared that in order to update the existing line items there are only 2 possible approaches.
1) Update the new custom [Product type] property for all existing line items manually
2) Update in batch via API
Using API will allow for bulk actions more easily but it does require someone who knows how to run endpoints
We can identify which product object the line item was created from by looking at a hidden line item property called hs_product_id. Identify the product ID from the product library by selecting the relevant product(s) > Export > Check the export file for the object ID
With the Product object ID, use the POST/crm/v3/objects/line_items/search to search through all line items to identify line items that originated from the product
After getting a list of line item IDs, you can then use the POST/crm/v3/objects/line_items/batch/update request to update the required property value of these line items in bulk
This would need to be repeated for each product in the product library
danke für die Bestätigung – also wäre wie eingangs vermutet die benutzerdefinierte Eigenschaft die Lösung. Insgesamt frustrierend, aber gut zu wissen, dass das Thema bereits HubSpot-intern berücksichtigt wird.
Viele Grüße!
Karsten Köhler HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer
bei mir funktioniert das – wenn ich ein Eigenschaftsfeld für das Objekt "Produkt" (Einstellungen > Eigenschaften) anlege, dann kann ich in einem benutzerdefinierten Bericht (Menü > Berichte > Berichte > Bericht erstellen) auch dieses Feld im Bericht verwenden.
Update: Ich habe gerade nochmal geschaut, die Standardeigenschaft für "Product type" ist tatsächlich nicht in Berichten verwendbar, warum ist mir auch nicht klar. Meine Empfehlung wäre hier, auf den HubSpot Support zuzugehen und nachzuhaken. Grundsätzlich müsste das Feld dort erscheinen, da auch benutzerdefinierte Felder im Bericht verwendet werden können.
Ein Workaround wäre, dass man ein benutzerdefiniertes Feld erstellt und dieses pflegt. Das erscheint dann in Berichten korrekt.
Viele Grüße!
Karsten Köhler HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer