For a custom two-sided landscape A4 booklet, a third blank page is appearing in between the cover and back pages. This is caused by the vertical height of the cover page report band being too long to fit the available canvas area. The solution is to calculate the maximum possible height of the report band and adjust accordingly.
In Report, Options in the top menu ribbon we can check that the paper height is 210mm. The top and bottom margins are both 10mm so deducting 20mm from 210mm gives us our maximum band height which is less than 190mm.
First we left click an empty area to select the band, then right-click to open the band options and view the height which is currently 200.03mm. The extra height is pushing into the next page so this needs to be reduced to 190mm. Note for this particular template the band needed to be reduced to 185mm to publish only two pages. It may help to adjust any objects contained within the band so that they don't protrude beyond the border.
In this example the lower banners should be lifted higher to reveal the full 10mm margin. The lower margin can be reduced slightly via Report, Options if your printer supports print to edge.
To free up precious server resources in Cloud servers here is a feed automation design for ListingsSynchronizer.
Synchro as a service
The server admin installs SynchroServer and creates the necessary Network Address Translation endpoints on the session host. Then SynchroServer is run as a service so that listings can still be transferred on demand when the server is idling, and a user account does not need to be logged in. This frees up significant resources for other workloads.
Cloned VM: the Jump Server
A small basic Windows virtual machine is created in one of our lab environments at SalesPartner HQ. The main data is backed up and restored into SalesPartner, then all photos are synced to produce a replica of the central server. This VM is the stepping stone or jump server where the data is processed and forwarded on to the website FTP server. An automatic transfer scheduled is established to persistently update the listings data at regular intervals.
The synchronization schedule is loaded to work alongside the ListingsSynchronizer app which forwards the data on to the website FTP destination.
Here are a few notes for importing a sales statistics CSV file from the REINZ website into SalesPartner.
In many flyer and report templates, icons are shown to represent how many bedrooms, bathrooms, garages, and living areas a property has. This guide looks at the scripting behind these icons which makes them show if the number is greater than zero, and hide if the number is zero or blank.
In this example template there are three script rules per icon.
Each element is uniquely named - this is how the script rules are linked back to the icons.
In edit mode right click on an icon, shadow, or data field and click Options to view the Name. Here are the image names for the bedroom icon's three related elements:
Now right click on an empty area of the same report band to view Scripts. Note the three lines of arguments which relate back to each of the bedroom elements. These SQL rules state that each item must only show if the number of bedrooms is not zero or blank.
SETBOOLPROP('ImageBed', 'Enabled', Listings.Bedrooms <> 0)
If you're swapping in new icons, you will probably need to rename each image with a unique name like 'ImageBed2' and then also copy and paste another matching rule into scripts. Often a name cannot be recycled.
If your rule is <> '' instead of <> 0, this will work if the Listing Entry fields are left blank, but if zeros have been entered (e.g for sections or bare land) then the number zero may appear on reports.
For an office's custom complex magazine template, anomalies began to occur where for various properties the icons would randomly show or hide. The solution was to rename all of the icon and numerical objects, and also rename them in the SQL script.
Yes - for REAXML uploads to company sites as well as portals such as Oneroof.co.nz, and Neighbourly the second agent is included in the feed data. As shown in the example XML script below the individual contact information is supplied for both salespeople. Individual salesperson photos are not uploaded from SalesPartner because those images are typically maintained separately via the website's admin control panel, and then linked to the listing agent's name.