Pim-community-dev: 1.6 Export filter by simple select

Created on 2 Nov 2016  ·  18Comments  ·  Source: akeneo/pim-community-dev

I'm reporting a Bug

Local Akeneo version: 1.6.4
Demo Akeneo version: 1.6.4

When adding a simple select attribute to filter products in the product export, the export completes instantly.

To reproduce in demo:

  1. Open a product, select a value in any simple select box.
  2. Go to export product
  3. Select this attribute and value as a filter
  4. Make sure that the other filters apply so that your product should be exported
  5. Click export

Result: export finishes instantly
Expected result: export to finish with at least 1 product in it (your product)

Can reproduce this on both ORM and MongoDB. If you need more info, I'm on slack :)

to reproduce

Most helpful comment

It's a setting that was causing this, it is not really a bug. However changing this setting on my production does not solve it. It solves it on the demo environment. So I am looking what is wrong on my end, so I can comment it here :)

All 18 comments

Pretty strange @janssensjelle

Yeah. It works fine for category filter or entities filter. But not simple select 😓

Hello @janssenjelle,

I did successful exports on our demo with a digital camera product and the "sensor type" simple select attribute. It's also work when I create a simple select attribute and follow your steps.

Can you provide me further information?

  • The product and the simple select attribute you used.
  • The complete product export job configuration.

Thank you in advance for your feedback!

Regards

@fabienlem this does seem to be due to the default completeness filter setting. I completely overlooked this in the demo.

I will test this on our production (MongoDB) and get back :)

@fabienlem used colors in the way @janssensjelle described and did not get results, even headers. May be i'm doing smth wrong as i have no experience working with 1.6 connectors but result is so

@a2xchip it is probably the completeness setting in this case. It is default set to must be complete

Hi @a2xchip,

I have tried with main color attribute with both MySQL and MongoDB and everything worked fine. As @janssensjelle said, I think it's linked to the completeness setting.

Regards

@fabienlem Means devs doesn't know how to use PIM's new exporter :smiley:

I'm sorry @a2xchip , but that's like a sneaky default setting they put in there :D

I think if we would record protected screencast and present it to @fabienlem it could make things much clearer. :eyes: @janssensjelle

It's a setting that was causing this, it is not really a bug. However changing this setting on my production does not solve it. It solves it on the demo environment. So I am looking what is wrong on my end, so I can comment it here :)

Right, so I've got an update, and was able to reproduce it on the demo

Steps

  1. Create a new product
  2. Do not assign this product to any category
  3. Create/edit an export profile
  4. Make sure the settings will match your product. Even defining your sku in the export list won't make your product export

To make the product show in the export

  1. Add the product to a category

I was able to reproduce this on demo.

Export settings:
screen shot 2016-11-08 at 17 04 14

Hello @janssensjelle!

The products have to be categorized to be exported. This prerequisite also exists in 1.5 version and our product team confirmed me that is a normal behavior.

To sum up, these are the conditions to export products:

| PIM 1.5 | PIM 1.6 |
| --- | --- |
| complete | match with export builder "Completeness" filter |
| enabled | match with export builder "Status" filter |
| categorized | match with export builder "Category" filter, "all products" option only works for categorized ones |

Regards,
Fabien

@fabienlem okay, thank you. Could the label "All products" be changed to "All categorised products", so this will be less confusing?

@janssensjelle you're right, a submitted an improvement suggestion to our product team.

Thank you for your feedback! :+1:

I could submit a PR if you'd like :-)

Thank you @janssensjelle! As wording could be a sensitive topic, I think it's better to wait for a product team feedback. I will let you know ;)

Hello guys,

1.7 is not supported anymore and this issue is almost 4 years old now. That's why i'm closing it, but do not hesitate to reopen it if needed.

Regards,
JM

Was this page helpful?
0 / 5 - 0 ratings