XMPie Audience Bug

[Laurent Tétreault]

Hi everyone,

I just install uCreate 10.1 with the newest version of InDesign (16.4). When i open a file and try to play with the Audience, it's doesn't work. Before i have InDesign (14.0.3) with uCreate 9.4 and it's work very good. 

I need help to resolve this case!

Thanks You in advance!

[couch]

If there is a bug, you need to report it to XMPie Support to get it fixed: https://na101.salesforce.com/sserv/login.jsp?orgId=00D300000000TRF

[west-digital.fr]

Hello,

"it doesn't work".

Would you like to elaborate, what does not work?

Is there any error message?

On our side, with CC-2021 (French), 10.1 on Windows 10 Pro, it looks everything works as expected.

In other words: not only can we still define your Audiences, but we can also use them (in Text or Style ADORs, per instance). 

See attached sample CPKG and output PDF.

west-digital.fr

[Paul Abney]

I know in October of last year. I reported that Audiences had an issue (case 00149660). Although the output works like it should, if you filter by audience, the Indesign document does not correctly show the filtered records. Not sure if this is the same issue. I don't have 10.1, but in 10.0 the problem still exists.

Paul 

[Laurent Tétreault]

The problem is not in the XMPie upload, it's on the InDesign document. When i want to filter Audience with the database, the file don't want to change the Audience (you can see the problem in the pictures i send). I don't have a error message, the upload in uProduce work perfectly. It's just the Audience filter.

Example:
You can see the School say = Law

The Audience filter say = Law

Put the modification i do in the document don't want to change (Law Good One.jpg it's the good one)

Maybe it's a bug with Indesign 16.4 + uCreate 10.1 but the software suppose to be update!

I'll ask my superior to do a bug review for help us if you can (and it's OK)

[Laurent Tétreault]

Sorry to be unpleasant, but anybody have a idea how to fix or i really need to ask XMPie for help??

Thanks in advance

[west-digital.fr]

OK, so... let's ease up a little bit, and try to clarify (or "On respire un grand coup", as one could say, in our respective Countries).

As a reminder, if needed: this Google Group is mainly a User-based community; meaning that, most members are XMPie customers, who ask questions or try to share their valuable experience with each-others. Fewer members, I think, are resellers, or genuine XMPie staff members. Anyhow, none are really committed in providing answers or solutions in a given period of time.

This means that, answers come are their own pace, based on the members free time, or level of expertise, or ability to understand the real context of a specific case. Anyhow, as you perfectly mentioned, as soon as your Company has a valid Maintenance & Support plan, any question or bug suspicion from yours will be warmly welcome by the XMPie Support Team (as you know, opening or updating cases can be done here or there - almost the same).

Having said that... as Paul wrote, there seems to be a bug in the "Audience" feature, or at lease something that does not work, as regular XMPie end-users (as you and me and Paul) would expect. Based on the CPKG that I shared earlier in this same thread, it"s true that version 10.1 does not seem to take the Audience filters into account (those set in the "Audience" pane), while you browse your recipients from the legacy "uCreate" pane (see my attached screenshot).

Again, only the XMPie Support Team would confirm that this is not working as XMPie thought it should.

So, in my modest experience, the best would be to raise a support case to the Support Team.

west-digital.fr

[Laurent Tétreault]

I love the answer you send me! I just want to see if i'm the only one who have this problem on the same version of me and i see you have it! So it'a confirm it's a XMPie Bug, my boss send a XMPie bug case and we wait!

Merci beaucoup de la réponse que vous m'avez donné!

Bonne journée

[couch]

On this problem with the audience feature, I heard that a bug has been raised by XMPie and that a fix will be created. At this point the fix is expected to be part of version 11. But, things may change and it is possible that a patch will be created before that.