Developer forum

Hey Morten.

It works if the ProductVariantID is an empty string, but not if it is null.

We have talked about adding "isNull" and "isNotNull" ( and maybe even an "isNullorEmpty and "IsNotNullOrEmpty" options to the filters, but I haven't heard anyone ask for them before now, so it hasn't yet been implemented/planned.

since null and the empty string are treated the same in that particular column, you can update the ProductVariantId column in your database to an empty string where it is currently null - then the export should work. Of  course, this is only really a useful solution if it is a one time export, and not one that is run periodically, to get new products from the system.

What destination are you exporting to? 

If your destination is an XML file, you may consider working around the problem by adding an XSL file that can filter the exported data as needed.

Hope this helps - if not, let me know, and we'll see what we can do to add the needed functionality to the Integration Module.

Regards, Jonas Dam

I would like it to be added to the integration module, why didn't you implement it anyway if you knew this could be an issue?

Hi Morten,

Your "like to have" is noted. We already have a work item regarding the implementation of filtering on NULL values. However, it will be prioritized on par with all other requests. As to why we did not implement it yet: because we do not have an infinite amount of resources.

That being said: the default value for VariantID is an empty string, so your filter should be working. The filter works fine on 8.2.2.7 on my local test site. If you cannot get it to work with this version (or later), please let me know - then we'll help you out.

If for some reason VariantID contains NULL values, simply make sure it doesn't. The column is part of a composite key and should at the least have an empty string (which as mentioned is default).

Regards /Snedker