0

Printing a VIEW ? This is how it can be done:

Since the release of the dynamic print layout in Ninox, it is now even easier to print out a VIEW:

 I have attached a sample database:

15 replies

null
    • Rafael Sanchis
    • Rafael_Sanchis
    • 7 mths ago
    • Reported - view

    You enable "Custom Json" where you use "JSON data input" formula : (click on the "fx")

    Sorry the question but here I got lost (Click ok the "fx")

      • Ninox partner
      • RoSoft_Steven.1
      • 7 mths ago
      • Reported - view

      Rafael Sorry for my lack of clarity. In the print editor of the dashboard table:

    • Rafael Sanchis
    • Rafael_Sanchis
    • 7 mths ago
    • Reported - view

    😮 Thanks 

    • Fred
    • 7 mths ago
    • Reported - view

      do you find it easier to use custom JSON then just the Ninox field names?

    One one table, I'm just trying to get a simple field:

    {d.CurrentTeamName}
    

    and when I click on print nothing happens. No new window opens, no new file is downloaded. It acts like I didn't click on the button.

      • Ninox Partner
      • RoSoft_Steven
      • 7 mths ago
      • Reported - view

      Strange, It should work also with the fieldnames:

      • Fred
      • 7 mths ago
      • Reported - view

      It is weird. I tried it on another DB and it took over 2min before the PDF popped up. I tried it in your DB and the PDF showed up within seconds. My main DB does not create the PDF at all. I've submitted an email to Ninox.

    • Rafael Sanchis
    • Rafael_Sanchis
    • 7 mths ago
    • Reported - view

    I Add some New client, on print editor I can see the new client but no in the image, I,m doing some bad or missing somthing.

      • Ninox partner
      • RoSoft_Steven.1
      • 7 mths ago
      • Reported - view

      Are you making the template with microsoft Word? You need to re-upload (with the command replace... when clicking on the template-name) the new file in the print editor to make it work.

      • Rafael Sanchis
      • Rafael_Sanchis
      • 7 mths ago
      • Reported - view

        OK Thanks. 👍

    • Alan_Cooke
    • 7 mths ago
    • Reported - view

    Why does your printout have a Carbonne watermark? I would love to start using dynamic printing but really struggling with printing views.  I do not understand the logic of 'rows' data.  Does one need a reference for each and every record in a view?  Or just the first two which tells Carbonne to continue for all records.
     

      • Ninox partner
      • RoSoft_Steven.1
      • 7 mths ago
      • Reported - view

       

      The watermark is for test-printing (with slider on in print editor)? this will not be deducted from your monthly dynamic print allowance (100 for starter and 500 for professional)

      Yes, Carbone will find automatically the pattern to repeat using the first row [i]) as an example.

      It would even worked like this:

      the row1,2,3.... are actually wrongly chosen by me, better would have been column1,2,3.... These are created on the fly in the formula below which contain the fields from your database. It is actually an easy way to rename field names with spaces to what carbone needs. i.e. there should be no spaces or special characters in it. More about carbone here.

      (select Clients where 'User#' > 100).{
          row1: 'First Name',
          row2: 'Last Name',
          row3: Email,
          row4: Phone
      }

      row1 contains the field 'First Name' and so on....

    • Fred
    • 7 mths ago
    • Reported - view
     said:
    this will not be deducted from your monthly dynamic print allowance (100 for starter and 500 for professional)

     Sadly, I get dinged for each test print. Luckily I don't do any.

      • Ninox partner
      • RoSoft_Steven.1
      • 7 mths ago
      • Reported - view

       Oh, Really? However, carbone offers its test prints unlimited in every price plan. This must probably be a bug in Ninox. I will check with Ninox support and get back to you on this.

      • Ninox partner
      • RoSoft_Steven.1
      • 7 mths ago
      • Reported - view

       Responce from support: 

      The error is known and is already being worked on intensively.

      It should be fixed with an update within the next 2 weeks.

      We don't know the version number of the update yet.

       

      • Fred
      • 7 mths ago
      • Reported - view

      yeah, sadly we will never find out when they do. it is so frustrating that they are so bad about communicating fixes.

Content aside

  • 7 mths agoLast active
  • 15Replies
  • 344Views
  • 5 Following