We have bought your software windward tag and about to go live and the pdf needs to mandatorily support tick mark instead of x mark.

Windward Support Team,

We have checkboxes to design user choices in Auto Tag Windward form, but when we generate the pdf , windward is not generating a user friendly checkbox UI element as part of pdf generation. Windward puts a x mark what we need is a tick mark

In the attached image it is indicated very clearly that at the top section where there is a x mark is what windward generates .

However what we need is a tick mark instead of x mark

Bottom line please provide us a programmatic solution for us to have checkboxes with a square boxes to show options along with a tick mark(no cross mark) next to the option , so that the generated pdf is clean .

Please do take this feature as just a silly UI unfortunately we are filing the case with govt of california and they require tick marks and not cross mark and this is a critical feature for our business and not a cosmetic feature.

Thanks and Regards
Rajesh Natarajan

Currently, if the Import tag is passed bad data (e.g. an image file doesn't exist or is an unsupported format), the only apparent way to prevent the report from breaking altogether is to set a default image. But what if we don't want a default image and just want the tag to be ignored if it doesn't like the data? Or what if the default image to be shown is also data-dependent?

I suggest two improvements:

1. That instead of displaying a default image, the tag could optionally be ignored altogether. In many cases, it would be preferable to have no image at all rather than a default placeholder. Particularly if we are generating a report with numerous full-page images that all happen to have bad data (e.g., if the image directory changed and no one updated the relevant data), we don't want page after page of the same default image.

2. That the default image could be data-driven. Our current solution for displaying product images in a report takes the image names from a field in the product table and concatenates them with a base URL from another field in another table. The reason for this is that if the customer moves their images to a different server, directory or whatever, they can change the base URL in one place and not have to update hundreds/thousands of records for individual images were the full URL hard-coded in the product data. While a single default image is far better than a broken report, it requires (a) that the customer actually has and wants a default image and (b) that the template would have to be updated if the default image gets moved or changed (instead of just updating a data field or two outside of the template). Changing a data field value carries a lot less risk than modifying a template.

Thanks for considering the idea.

We are having a lot differences between the Word output and that generated by Windward PDF. Spacing can be different and sometimes the PDF does things wrong that Word does correctly, such as text going through a footer or the PDF not breaking the page correctly when using Keep with Next. It seems to me a lot of defelopment time goes into trying to make the PDF output better.
In literally every instant, the PDF from Word's Export feature worked correctly. Also, the output is half the file size, which is also very important for us.
A lot of our issues would be solved if we could just have Windward generate through Word's Export to PDF feature. Or perhaps another commercial PDF converter.

When using the RESTful Engine with an expired license the application throws a 500 with an unhandled exception. I would suggest you improve your application by catching your exceptions and throwing meaningful error codes and messages to the client.

I get the exception when calling the version endpoint with an expired license. I tried uploading the Postman response but that doesn't work either. Below is the stack trace.
[LicenseException: Expired license key ]
net.windward.xmlreport.ProcessReport._init(Boolean ) +6115
net.windward.xmlreport.ProcessReport.init() +26
net.windward.api.csharp.Report.Init() +24
RESTfulEngine.WebApiApplication.InitLicenseAndEngine() in C:\agent_work\1\s\restfulengine\RESTfulEngine\Global.asax.cs:87

[HttpException (0x80004005): Expired license key ]
System.Web.HttpApplicationFactory.EnsureAppStartCalledForIntegratedMode(HttpContext context, HttpApplication app) +520
System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers) +176
System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context) +165
System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context) +267
System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext) +341

[HttpException (0x80004005): Expired license key ]
System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +523
System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +107
System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +688

Hello,

Right now when working with a scatter chart in Word if you have different sizes for the markers they will be shown as different sizes on the plotted area, but in the legend the marker sizes are the same size.

In the attached picture 1 and 2 have different sizes on the plotted area and in the legend they are the same size but smaller. Right now only marker sizes 3 and 4 behave normally (the marker size is the same on the plot and in the legend).

I was told that this is a known limitaion.

Can you update the software in such a way that the marker size changes on both the plot and the legend?

Thanks!