Something like the above would be desirable, so how do we go about doing this output? Well, it so happens there are a few ways in which you can do this. Ideally what we would want to do is have each type of question output in its own correct format, completely independent of the format of other question types. In this situation it makes no sense to have every record appear exactly the same, because that would make the test useless to the person looking at it. What if we were printing a test, where questions could be one of 3 different types? Some questions may be multiple choice, others a short answer, and others may be longer paragraph answers - with each record being a question. Fields appear in their respective columns, and all look pretty similar, nothing fancy going on here.Ĭonsider now a different printing scenario. By that we mean the same fields in the same columns with consistent formatting.Ībove is an example of a standard report output. If you are printing a simple list of customers for example, then you would expect the appearance of information on each line of the output to be the same. But what if we want records to print with a completely different output design depending on the type of record? In this article we detail some of the various ways in which this can be achieved, and the pros and cons of each method. It does not store any personal data.Most of the time when we print records in FileMaker, the output of every record appears pretty much the same, with similar formatting and design. The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. The cookie is used to store the user consent for the cookies in the category "Performance". This cookie is set by GDPR Cookie Consent plugin.
The cookies is used to store the user consent for the cookies in the category "Necessary". The cookie is used to store the user consent for the cookies in the category "Other. The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". The cookie is used to store the user consent for the cookies in the category "Analytics". These cookies ensure basic functionalities and security features of the website, anonymously. Necessary cookies are absolutely essential for the website to function properly. This simple modification will ensure that your web viewer displays your FileMaker data consistently and accurately.
This will convert special characters into html friendly text that won’t break your web viewer.ĭata = GetAsURLEncoded ( ) Luckily, this issue is easily fixed using one additional FileMaker function! To get our data to display properly in the web viewer, we’ll simple wrap our data source in the ‘GetAsURLEncoded’ function.
All of a sudden and seemingly out of nowhere your web viewer will be “broken” and will no longer display the data correctly. Most likely, you will not notice anything wrong right away, until the day a user types a special character (specifically the ‘#’) into your data source. We will use one for our example, but it isn’t necessary to accomplish our goal. Implementing this the right way is key to making sure your web viewer doesn’t “break” down the road.Ī common way to display data is to use a ‘Let’ function. Using a web viewer to display FileMaker data is one of the easiest and most versatile ways to enhance the functionality of your FileMaker app.