Publisher 2.0.4 (Windows) DataMerge issues

[no spam]

Hi, I really loved Publisher until V2.

 Just updated to Publisher 2.0.4  to find the good old bug (or feature) to still be there and worse

1. Opening an afpub file originally created with some version 1 O still cannot edit anything inside a textfield that is linked to a data source (xlsx) via datamerge. 

2. One could say, yes its linked… thats why… BUT in version 1 I could. Leading, Fontsize, Fonts.

3. Linebreaks. Publisher Version 2 does not do the same linebreaks as version 1. And they cannot be corrected. Also it does not respect linebreaks that are already in the datasource.

4. Finding DataMerge in V2 took some moments, why was it moved? Relearning interfaces is no fun.

5. Finding the „fields“ window was really a drag, has to open „help“. Why was it moved and why hidden in a submenu? Nobody will look there, I promise.

6. The old bug, still being there is that when changing the datasourcepages in Datemerge window, the fields sometimes do not get updated, or only some. Only solution (still the same as in V1) is to zoom into the document and back out again to „refresh“ its rendering on screen. Very sad. I had reported this several years ago already.

 

In general this means to me, I should not have bought V2. Its unusable for me. Please revert the tool back to its original funtionality.

Best regards.

 

[stokerg]

Hi @no spam,

1 hour ago, no spam said:

1. Opening an afpub file originally created with some version 1 O still cannot edit anything inside a textfield that is linked to a data source (xlsx) via datamerge. 

 

Can you attach a sample .afpub file?

1 hour ago, no spam said:

3. Linebreaks. Publisher Version 2 does not do the same linebreaks as version 1. And they cannot be corrected. Also it does not respect linebreaks that are already in the datasource.

 

We do have an issue logged where line breaks are ignored in certain data sources.  What format is your data source in, if you can attach a sample that shows the issue that would be great.

1 hour ago, no spam said:

4. Finding DataMerge in V2 took some moments, why was it moved? Relearning interfaces is no fun.

 

The whole interface for V2 was redesigned, so not just data marge was moved.

 

1 hour ago, no spam said:

6. The old bug, still being there is that when changing the datasourcepages in Datemerge window, the fields sometimes do not get updated, or only some. Only solution (still the same as in V1) is to zoom into the document and back out again to „refresh“ its rendering on screen. Very sad. I had reported this several years ago already.

 

I'll give this report a nudge and see if i can get any update on this.

 

 

 

[no spam]

18 minutes ago, stokerg said:

Hi @no spam,

Can you attach a sample .afpub file?

We do have an issue logged where line breaks are ignored in certain data sources.  What format is your data source in, if you can attach a sample that shows the issue that would be great. 

The whole interface for V2 was redesigned, so not just data marge was moved.

18 minutes ago, stokerg said:

 

I'll give this report a nudge and see if i can get any update on this.

 

 

 

well. the data source is an Excelfile, xlsx (latest version of Excel). Files attached. Afpub created with V2.0.4

test-datasource.zip

[no spam]

Any News on this? cheers.

[PaulEC]

1 hour ago, no spam said:

Any News on this? cheers.

Just a thought, but have you updated to 2.1 to see if it has been fixed?

[no spam]

Yes I did update. None of the bugs I have reported here so far have seen any improvements/solutions.

Cant edit the entries, change the linespacing/leading/content. Nor does it update correctly when going thru different records usong the preview „backwards“ and/or forward buttons.

Still have to zoom in and out again to force a redraw of that previewed page. (This is a good old bug from V1, some years ago).

If it were not for Photo and Designer I‘d try to get anredund by now for version 2. Disappointing.

And yes, Its all plug in, has power and I did a restart and have all the latest updates on Windows 10.

No, I wont try Windows 11. cheers.