Not sure if I was very clear with my original description of the problem judging by the lack of response :) so I though I'd add a few pictures to show what I mean..........
Tags can be used in the configurator description:
And I want to use them here where I have some HTML tables stored...... Currently I have to create a unique table for each product where if I could have an HTML table containing product tags then I would only need to do it once and it would just populate with Linnworks data.
This is Ethan from HyperCommerce.
Aren't you able to just put this
within your Metafields Values and access these?
If you need custom solutions such as Advanced SQL Queries, Custom Reports, API Solutions or Integrations, please feel free to reach me at firstname.lastname@example.org
Sadly not they only work in the description not the metafields... which is a shame because it causes a lot of work when it's a pretty simple solution.
to add to that... when I do what you suggest the tag appears in my table instead of the number that I'd like to appear
I discussed this topic in a technical session at LA2018 and was suggested to post it on here - good show by the way!
I have recently started using the configurators for Shopify, the tags feature in the product description section is useful as it allows me to add variables like weight and dimensions already stored in Linnworks.
My Shopify template product page has tabs that are populated by Metafields. Linnworks allows me to create/populate these metafields from within the configurator which I have used and works great - however, I've found that the description tags don't work there.
2 of my tabs are for product dimensions and package dimensions, at present I have to create an HTML table for each product to show this data, if I could use the description tags in the metafields it'd mean I could just add a table template populated with Linnworks tags to the configurator template and the tables would create automatically.
I appreciate this may be quite a specific case but the functionality is already there and implementing it wouldn't affect any other systems (as discussed with LW staff!). That said I'm sure there are others that would benefit from the functionality in many different ways as it really would make the system
Looking forward to your thoughts!
1 person likes this idea