Filter issue

[ogster1974]

Hi Guys

I have an issue around the use of filters in my report.

Environment is NPrinting 17.3.

I'm generating a excel report with 2 levels in it.

When I set a country or region filter the report generates fine.

When I set the filter to the user key which happens to be an email address I get the dreaded Sequence contains no elements error.

Can you point me in the direction of the inner exception details as the logs i've looked at are not very useful to troubleshoot with?

Regards

Andy

[ogster1974]

Trying a number of different filter types it definitely seems to be the use of an email or the @ symbol that seems to be causing NPrinting to act up.

I'm going to replace the key with another value with the same level of uniqueness and see how I get on.

[Lech_Miszkiewicz]

I know that this is not a direct answer to your issue, but i strongly suggest to upgrade. You are on very old, buggy version (i think you are like 12 versions behind!).

If you have not used the recent versions you are not even aware how much you are missing!

Troubleshooting your issue would also be easier by looking at task execution preview which would indicate what filter is not applied.

cheers

Lech

[Ruggero_Piccoli]

Hi,

I agree with Lech. You must upgrade to the most recent version by following official instructions before to go ahead with the problem investigation. A log of bugs are solved between 17.3 and February 2019, some about filters so we must be sure that you are benefit of all of them before proceeding.

Best Regards,

Ruggero

[ogster1974]

I agree we are well behind on releases. I have raised this and reccomend that this happens. In the mean time I have to deliver on the environment I have.

[ogster1974]

Ideally yes but I haven't got the time to wait for this to happen. I have raised a request for the environment to be upgraded before this issue was identified. In the mean time I have to get on and deliver on what I have. I'm testing my work around today.

[ogster1974 · Accepted solution]

Just to close this thread the workaround I put in play by generating the key replacing the @ symbol solved my immediate issue.

Not sure if this has been resolved in later releases but one for another post.