Jump to content

Recommended Posts

Posted
It has happened when I use the data merge tool that when importing data from a table when it comes to dates in the format 
of my country: dd/mm/yyyy , when importing the data, Affinity Plubisher subtracts one unit from the day. becomes dd-1/mm/yyyy. 
I've already reinstalled the program (I use version 2.57), 
I've disabled acceleration using the graphics card and I've used other table formats. 
But I only managed to solve it by changing the format in the table to dd/mm/yy. 
It seems that when the year is in two digits the program reads the table normally.
 
Posted

Hi @m job,

It's working correctly here having checked it on Windows and Mac... What time zone is your Windows PC set for...

Could you upload your data file or even a subset of it so we can see why this might be happening?

Affinity Designer 2.6.0 | Affinity Photo 2.6.0 | Affinity Publisher 2.6.0
MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

Posted

Hi @m job,

Many thanks for the files...

If you select Update in the Data Merge Manager you may (or may not) see a message saying Data Merge Update Failed, Could Not Open File...

Either way, if you delete the Excel file and then re-add it the dates are then shown correctly for me in the Publisher file.

Affinity Designer 2.6.0 | Affinity Photo 2.6.0 | Affinity Publisher 2.6.0
MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

Posted

Thx for idea Hangman, but selecting "Data Merge Manager" (under "WINDOWS") within Affinity, deleting the Excel data form I'm using and then adding it again didn't do anything. Still date - 1... Hmmm

Thoughts anyone?

 

Posted
3 hours ago, jtclat said:

Thx for idea Hangman, but selecting "Data Merge Manager" (under "WINDOWS") within Affinity, deleting the Excel data form I'm using and then adding it again didn't do anything. Still date - 1... Hmmm

Hello and welcome to the forums.

Can you explain a bit more precise what you try do do, please?

MAC mini M4 | MacOS Sequoia 15.3.2 | 16 GB RAM | 256 GB SSD 
AMD Ryzen 7 5700X | INTEL Arc A770 LE 16 GB  | 32 GB DDR4 3200MHz | Windows 11 Pro 24H2 (26100.3194)

Affinity Suite V 2.6.1  & Beta 2.6 (latest)
Interested in a free (selfhosted) PDF Solution? Have a look at Stirling PDF

I already had a halo, but it didn't suit me!

Posted
14 minutes ago, Komatös said:

Can you explain a bit more precise what you try do do, please?

Can you explain a bit more precisely what further information you are trying to elicit, please?

Alfred spacer.png
Affinity Designer/Photo/Publisher 2 for Windows • Windows 10 Home/Pro
Affinity Designer/Photo/Publisher 2 for iPad • iPadOS 17.5.1 (iPad 7th gen)

Posted
5 hours ago, jtclat said:

Thx for idea Hangman, but selecting "Data Merge Manager" (under "WINDOWS") within Affinity, deleting the Excel data form I'm using and then adding it again didn't do anything. Still date - 1... Hmmm

Thoughts anyone?

Strange...

This is what I'm seeing... and the merged data file shows the correct dates...

Affinity Designer 2.6.0 | Affinity Photo 2.6.0 | Affinity Publisher 2.6.0
MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

Posted
12 hours ago, Hangman said:

Strange...

This is what I'm seeing... and the merged data file shows the correct dates...

 

No they are no the same. In the source table we have 03/02/2019 and in the data merge we have 02/02/2019 you see? The same mistake hapens in the outher registers in this field " DATA DE NASC.". The next date will apear with de first nunber of date -1.

Posted

This is definitely a bug in the Windows version! 

I have tested it on Mac and Windows too.
The date is displayed correctly on the Mac. On Windows, the date is displayed incorrectly.

 

MAC mini M4 | MacOS Sequoia 15.3.2 | 16 GB RAM | 256 GB SSD 
AMD Ryzen 7 5700X | INTEL Arc A770 LE 16 GB  | 32 GB DDR4 3200MHz | Windows 11 Pro 24H2 (26100.3194)

Affinity Suite V 2.6.1  & Beta 2.6 (latest)
Interested in a free (selfhosted) PDF Solution? Have a look at Stirling PDF

I already had a halo, but it didn't suit me!

Posted
3 hours ago, Komatös said:

The date is displayed correctly on the Mac. On Windows, the date is displayed incorrectly.

Is this before or after updating the data source...

When first opening the file on Windows or Mac, the Excel data file link is shown at its original location, i.e., D:\OneDrive\#documentos\#Ed Art\#planejamento\... In Publisher, this results in the Date shown as Date -1 in the Data Merge panel, Fields Panel and the date mirrors this when you run the Data Merge, i.e, Date -1

If you update the data source so the link to the Excel file is now shown as your local Hard Drive, the date in the Data Merge and Fields Panels mirrors that of the Excel file and the Data Merge reflects this, i.e., the Date is shown correctly...

13 hours ago, m job said:

No they are no the same. In the source table we have 03/02/2019 and in the data merge we have 02/02/2019 you see? The same mistake hapens in the outher registers in this field " DATA DE NASC.". The next date will apear with de first nunber of date -1.

In which case I'm wondering whether this is a regional settings issue... Your Excel file is stored on OneDrive but we have no idea where the Data Centre is located...

When I open your Excel file it shows the dates formatted as *14/03/2012. Date formats that begin with an asterisk (*) respond to changes in regional date and time settings that are specified for the operating system.

https://d13ot9o61jdzpp.cloudfront.net/images/regional_settings.jpg

Try the following...

  1. With the file located on OneDrive change the Date formatting in the Excel file from *14/03/2012 to 14/03/2012 (i.e., without the asterisk), resave and then update the data source in Publisher. Is the Date still shown incorrectly?
     
  2. If it is, download the Excel file (and Publisher file if it's also located on OneDrive) so it is located on your internal Hard Drive and then update the Data Source in the Data Merge Manager in Publisher. Does this still show the Date incorrectly as Date -1 in Publisher and the Data Merged File?
     
  3. If it does then with the Excel file located on your internal Hard Drive, export it as a CSV file and replace the Excel file with the CSV file in the Data Merge Manager. Is the date still shown incorrectly?

This is what I see on Windows after updating the link to the data source to my internal Hard Drive, same on Mac...

Affinity Designer 2.6.0 | Affinity Photo 2.6.0 | Affinity Publisher 2.6.0
MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

Posted

I confirm, the date value is only displayed incorrectly before updating the data soucre location. After updating the MacOS and Windows versions of Publisher display the date values correctly.

 

MAC mini M4 | MacOS Sequoia 15.3.2 | 16 GB RAM | 256 GB SSD 
AMD Ryzen 7 5700X | INTEL Arc A770 LE 16 GB  | 32 GB DDR4 3200MHz | Windows 11 Pro 24H2 (26100.3194)

Affinity Suite V 2.6.1  & Beta 2.6 (latest)
Interested in a free (selfhosted) PDF Solution? Have a look at Stirling PDF

I already had a halo, but it didn't suit me!

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.