A computed value in process.js doesn't show up in the PDF

Check, in order:

1. Did you assign it onto inputs, not a plain local variable?

   // Wrong - nothing outside this script will ever see myData.
   var myData = inputs.options.map(...);
   
   // Right - a NEW property on inputs, visible to any block afterward.
   inputs.myData = inputs.options.map(...);
   

   See process.js -> Handing computed data to blocks.

2. Is the property name actually new, not the same as an existing submitted field? Reassigning inputs.options = ... is silently ignored - compute into a different name (inputs.optionsFormatted, inputs.gridData, whatever's clear).

A block renders nothing, with no error message

Usually by design, not a bug - several block types quietly omit themselves rather than showing a broken placeholder: an image/signature block with a missing/unset source, a QR block whose data evaluates to an empty string, a grid block whose data expression evaluates to an empty array (or errors - a broken expression inside a grid's data fails silently, same as everywhere else block templates run). Double-check the field/expression actually has a value for the data you're testing with.

For everything else (JSON syntax errors, autocomplete not suggesting, layout looking different in the editor vs. the printed PDF), see Troubleshooting.