Custom date formatting for fields

[anto]

3 minutes ago, walt.farrell said:

What application did you use to create the file you shared with us? Can you open that test file in that application and show us the Date-formatting options you used?

I have created it in LibreOffice

[anto]

here what shows Excel

[walt.farrell]

Here's what LibreOffice shows for me with your file, @anto:

[Hangman]

It sounds like a regionalisation issue but I can't be sure... @anto, if you change the language from the Format Cells dropdown to either English or English (USA) and then ensure the data format still appears as dd.mm.yyyy or if not, change it so it does and re-export your .xlsx file does that make any difference once loaded into Publisher?

[anto]

5 minutes ago, walt.farrell said:

Here's what LibreOffice shows for me with your file

If you read the note that Excel provided about *, it probably depends on the regional settings.

Then where is the error? Who is doing something wrong?
LibreOffice is formatting incorrectly, or the Publisher is reading the regional settings incorrectly

[MikeTO]

Dashes versus periods are due to the language.

 

 

[walt.farrell]

28 minutes ago, Hangman said:

It sounds like a regionalisation issue but I can't be sure...

If I specifically tell LibreOffice that the cells are Date format, and Ukranian language, I get the . separators that @anto expects, and it works in Publisher after that, too.

[anto]

i have opened and saved this file in Excel. And then opened in LibreOffice.

With this format DD\.MM\.YYYY;@ Publisher works.

What this mean?

[MikeW]

Here, using Excel or LibreCalc, it displays as Anto wants, whether I save the file or not. Here, it shows as a custom format. Screenshot is from Excel.

If the issue is that APub cannot deal with custom formatting expressions, that needs changed.

[Mr. Doodlezz]

Hey everyone!

Is there a feature or workaround for automatically setting a date to display a date that is N days in the future from the current date?
What I mean by that is something like this:

Definition: dd.MM.YY +Nd
Example: dd.MM.YY +30d for today would get converted to and effectively displayed as 19.11.2023 (20.10.2023 + 30 days).

Thanks!

[MikeW]

6 minutes ago, Mr. Doodlezz said:

Hey everyone!

Is there a feature or workaround for automatically setting a date to display a date that is N days in the future from the current date?
What I mean by that is something like this:

Definition: dd.MM.YY +Nd
Example: dd.MM.YY +30d for today would get converted to and effectively displayed as 19.11.2023 (20.10.2023 + 15 days).

Thanks!

Of course. Have you tried using a search engine?

https://letmegooglethat.com/?q=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dexcel%2Bfuture%2Bdates%26sourceid%3Dchrome%26ie%3DUTF-8

[MikeW]

But if you meant inside APub? No cells can be calculated.

[Mr. Doodlezz]

I was focusing on an option within Affinity Publisher since we're in the thread (regardless of all previous spreadsheet comments) for custom date formatting in Affinity, aren't we? 🤨

[MikeW]

7 minutes ago, Mr. Doodlezz said:

I was focusing on an option within Affinity Publisher since we're in the thread (regardless of all previous spreadsheet comments) for custom date formatting in Affinity, aren't we? 🤨

The thread changed from being able to format dates in APub to custom formatting in Excel not being transferred into APub during a data merge.

But the answer is the same--there is no option that I understand for calculated future dates (no spreadsheet-like calculations at all). Without creating a sample, I don't know if an Excel sheet using such calculations would come in intact, either.

[Mr. Doodlezz]

52 minutes ago, MikeW said:

The thread changed from being able to format dates in APub to custom formatting in Excel not being transferred into APub during a data merge.

But the answer is the same--there is no option that I understand for calculated future dates (no spreadsheet-like calculations at all). Without creating a sample, I don't know if an Excel sheet using such calculations would come in intact, either.

Sure, a lot of people have taken the discussion in a different direction. Maybe those folks just aren't the right ones to answer my question since I'm not bringing up spreadsheet tasks or issues with data merging.

I'm asking about the feature that this thread originally focused on, and I believe it still does, according to the first page and the thread's title. It's still custom date formatting for fields started by Ash to highlight and help with this exact feature, isn't it? (Just wondering if it’s actually me being the one off-track with my question here.)

Anyway, you might be right, and there seems to be no way to achieve what I want, at least none that I've found, which is similar to what =TODAY() + 30 does in Excel – too bad!

[walt.farrell]

4 minutes ago, Mr. Doodlezz said:

I'm asking about the feature that this thread originally focused on, and I believe it still does, according to the first page and the thread's title. It's still custom date formatting for fields started by Ash to highlight and help with this exact feature, isn't it? (Just wondering if it’s actually me being the one off-track with my question here.)

The topic is about being able to format the actual date/time values in different ways, not about being able to calculate using dates.

[amcd]

The Time/Date fields in latest version of Publisher 2.3.1  - DEFAULTS to UK GMT.

Unfortunately with your new standard,  I have lost my ability to easily format date/time fields that I had been using for years.

I am in Brisbane, Australia which is Australian Eastern Stand Time (AEST) i.e. UTC/GMT +10 year round . Sydney is currently  Australian Eastern Daylight Time (AEDT=AEST+1) i.e. UTC/GMT +11 during summer.

I tried using Ash's table (26 June 2023) for some hours with no luck.

Please can you direct me to a tutorial or easy instructions that shows me how to edit the time/date fields.

I would be very grateful if you would send me specific examples of Field Formatting for Brisbane and Sydney.

Many thanks amcd

[MikeTO]

16 minutes ago, amcd said:

The Time/Date fields in latest version of Publisher 2.3.1  - DEFAULTS to UK GMT.

Unfortunately with your new standard,  I have lost my ability to easily format date/time fields that I had been using for years.

I am in Brisbane, Australia which is Australian Eastern Stand Time (AEST) i.e. UTC/GMT +10 year round . Sydney is currently  Australian Eastern Daylight Time (AEDT=AEST+1) i.e. UTC/GMT +11 during summer.

I tried using Ash's table (26 June 2023) for some hours with no luck.

Please can you direct me to a tutorial or easy instructions that shows me how to edit the time/date fields.

I would be very grateful if you would send me specific examples of Field Formatting for Brisbane and Sydney.

Many thanks amcd

Hi, are you using macOS Sonoma? There's a known issue with Sonoma and time zones. Serif has it on their list but it may be something Apple has to fix.

 

[amcd]

Yes I am using macOS Sonoma.  I am not convinced this is an Apple issue.

I no longer have Ventura on my Mac. I will try on Monterey.

 

[amcd]

Apart from this time/date issue.  I am also experience quite a lot of instability with latest Publisher 2.3.1 app on Sonoma 14.2.1. 

I can only clear various issues by restarting.  Publisher. This is costing me a lot of time.

Please, where can I can I download a previous  .dmg of Publisher 2 for the time beings since the problems have only hit me with Publisher 2.3.1

Many thanks

amcd

[anto]

3 hours ago, amcd said:

Please, where can I can I download a previous  .dmg of Publisher 2 for the time beings since the problems have only hit me with Publisher 2.3.1

here is

https://store.serif.com/en-us/update/macos/publisher/2/

[Affinity Info Bot]

The issue "Update button for 'Current Date & Time' field fails if text frame is placed on a master page" (REF: AF-4201) has been fixed by the developers in the latest beta build (2.6.0.2805). The fix is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Affinity Info Bot to notify us.