R C-R

I'm not sure what you want to accomplish.
Data Merge Fields always come from the Merge file (xlsx, csv, json), and Section Names come the Section Manager. You could certainly have a field in the Merge Source named Section Name, but it's totally unrelated to what you configure in Section Manager.

EDIT: I just noticed the OP is a Windows user, but I'll leave the macOS related stuff here because I think there is something similar to wired memory in Windows.
The only memory that can't be cached to disk is the wired memory the macOS system needs to operate -- more about that & memory usage in general can be found in this Apple article, including a bit about why memory remains cached to improve performance, & why you can't force the system to use less memory than it needs.
As I understand it, the RAM limit in the Affinity apps is provided to be able to 'tune' the app to use less memory that it otherwise might when a user is running the Affinity app plus other memory-hungry apps simultaneously, thus potentially reducing disk thrashing. But it may have other uses as well, because it is sometimes suggested that reducing it from the default has helped prevent certain odd behaviors, instabilities, & maybe even some obscure causes of crashes.

Looks to me that you didn't read the above referenced FAQ thread, as removing the APh UI setting from macOS via the macOS defaults system settings doesn't need a running APh app at all here!
So open the macOS Terminal.app and perform a "defaults delete com.seriflabs.affinityphoto" CLI command call ...
... if that gives back a possible 'Domain not found' error when using the above Terminal command, then you have to delete the APh plist file manually. Perform therefor in the terminal then instead the following ...
... OR alternatively navigate with Finder or some other macOS File Browser to "~/Library/Preferences" and delete manually the "com.seriflabs.affinityphoto.plist" property list file.

Except via the Layers panel, of course  

If your Text Frames were on a Master Page, it would be easy to add the Layer once and handle all of them.
Learning how to use them properly will pay off in the end, I think.

To enable PDF logging on macOS:
Quit Affinity Start Terminal Type the below (ensuring you change 'yourusername' for the name of your user folder) and press Enter to execute the command launchctl setenv PDFLIBLOGGING "filename=/Users/yourusername/Desktop/PDFLib.log" Run Affinity and export to PDF and then click OK to accept the error message Go to /Users/yourusername/Desktop and send the newly created PDFLib.log to the support team as requested.
(Ensuring you change yourusername as required) To disable PDF logging on macOS:
Quit Affinity Start Terminal again Type the following to stop the logging and to return your settings back to normal launchctl unsetenv PDFLIBLOGGING

Looks like a bug. Serif Info Bot has posted to this thread (a hidden post has been made for staff to link to the bug Nathan has acknowledged). If it's a hidden automated post then you should not be notified, but it looks to me like if you are to be notified of replies by visible users the forum software includes posts you cannot see too.

Stands for dyslexia and or 12 hours of work and or FFF (Fat Freaking Fingers) and or Posters Original. 

I think you are never going to get a 'one size fits all' answer for this because there are too many different workflows & kinds of projects for that to be meaningful.
So if you can tell us more about the kinds of projects you want to do it would help narrow down the possibilities.

If you search these forums on "EXE based installers" one of the hits from the FAQ section is this:
 

The screen is only a fixed size in relation to your document. Think of the screen as a window on your document. If your document is larger than your screen you can scroll around it, or zoom in or out.

How can you make a document that has a different aspect ratio than the screen cover the full screen?

canon ip8750 site:forum.affinity.serif.com  

Did you try the Tab key, as @R C-R suggested above?

From what I have read in the forums, it seems that there are many different models of Canon & perhaps other brands of printers that will do borderless printing only for certain paper sizes, but the additional "non-canon genuine art paper" limitation seems like an odd one.
Perhaps this has something to do with ink spilling/leaking into other parts of the mechanism?

I have instal it  4 times new ..same error ..i found a map on pc that saves the instal when i remove the program ..a cleaner after removing this file and intal new from the serif inlog site ..same..i try some buttons to  for look where i can fix this... i think in the prigram you dint need to stay online for the affinity progam..i logt out..and i think thats alsow the problem ..its strange ..i got te menu bar back .. thanks for theb suport 
Jacq22

@Dan C and @R C-R, my apologies... I exported the Cracked Heart.afdesign file as a Press Ready pdf, opened it alongside the original Designer file and then got involved with a different issue. When I came back to it, without thinking I exported the PDF version which of course had now adopted a working profile and therefore exported regardless of the PDF Preset... 😜

The icon symbolizes the adjustment type.
https://affinity.help/photo2/English.lproj/index.html?page=pages/Adjustments/adjustment_applying.html?title=Applying adjustments

There is no issue with the contents of thomasos post above.
They are simply another user of the Affinity forums and have as much as right as anyone, including yourself, to post here.
If you don't wish to see replies from specific users, please use the Ignore function. As I understand this should mean the replies from this user are hidden to you. It does not 'block' their ability to post within your thread (nor should it).
Please do not '@' tag myself or other forum moderators like this publicly if you have an issue with a post or a user, use the built-in report function of the Forums and this will be dealt with as required.
 
I am locking this thread from further replies. I hope you all enjoy your weekend.

It's an easy mistake to make if you have closed but not quit the app. I gather that isn't possible on Windows but on Macs there can be a big difference between the two, depending on if the app automatically quits or not if its last or only window closes.
BTW, also note that you have to quit the app again for the launchctl unsetenv command to take effectto return things to normal.

I am sorry for this false information: it seems I made the same mistake as R C-R, since when I tried it again, this time certainly with Publisher quitted, the PDFlib log has been well created. 

There can be issues working with files that are not on a local directory, so be prepared for that and make sure you keep backup versions of your files.
Also, for working with text, you need to have all the same fonts and versions of those fonts installed on all the machines (though, with Publisher, you can create a Package that includes the needed fonts, which will be installed automatically while you work on the file).

Works fine with an iPad and a local network with Windows machines and NAS devices.

The V2 apps all came from the Affinity Store. AD & AP V1 came from the MAS. APub V1 came from the Affinity Store. I just checked again & all 3 V1 apps generate a PDFLib.log file, but the V2 apps still do not for me, so I'm still mystified by why it isn't working.
The only thing I have not yet tried is quitting & restarting any of the V2 apps on my Mac. I would prefer not to try that because of the still very annoying bug that clears the recently opened items on the Dock popup, but I will give that a try for one of the V2 apps if you think that would make any difference.
EDIT: AHA!!! I quit AD V2 & restarted it after using the Terminal command & now the PDFLib.log is created for that app but not for the other two V2 apps.
So it seems that enabling logging won't 'take' if the app is already running, but quitting & relaunching them will.
Mystery solved ... I think. 😃
EDIT 2: It's the same for the launchctl unsetenv PDFLIBLOGGING command: If I use it when the app is still open, it has no effect & the log file is still created or appended to. Very annoying that I have to do that because of the Dock clearing bug, but at least I now know the cause & cure for the logging issue.

Personally, I find nothing uncomfortable about using it & since it also works the same way in AD or AP as well as in the Designer or Photo persona of APub, I think it is fine as is. But as always, YMMV.