Hello everyone,
I have had the FAZ uplifted to the above firmware and now I am getting ::fff appended to all the reports, I even went to the built in chartbuilder after having done a search on source and destination and still get the ::ffff. Any ideas how to fix this ?
When you clone a report in FortiAnalyzer, it clones the report container, not the child dependencies. The cloned report simply references the existing chart library elements and underlying SQL datasets. If you edit a chart's layout or modify the SQL inside a dataset, you are editing the global object and modifying the original report simultaneously. Fortinet should change that CLONE button to something else, that CLONE button does not clone the underlying SQL datasets etc, very misleading and cost someone a lot of time.
Hi everyone,
I am rebuilding an engine and wondering if anyone has used aftermarket kits from china for piston and cylinder such as : 12100-KZR-600
I have previously used after market variator and belts and done 15 miles on it and had astounding peformance, therefore wonder if the piston cylinder kits are any good ?
Anyone else agree when uplifting to new firmware on the FAZ the annoying generic one liner error is appalling when attempting to troubleshoot SQL datasets:
Invalid SQL query. Please check the syntax.
This generic, single-line error is arguably the most frustrating aspect of writing custom datasets in FortiAnalyzer. When a system provides zero context, zero line numbers, and zero indication of what exactly failed, it completely breaks the standard developer workflow and turns a simple typo into a multi-hour troubleshooting session.
Here is why this single-line output makes debugging almost impossible:
The primary issue is the complete lack of spatial awareness. In a standard SQL environment, if you miss a comma or mistype a function, the database engine returns an exact coordinate—such as "Syntax error at or near 'FROM' on line 14, character 22." This allows you to instantly locate and fix the typo. FortiAnalyzer’s single-line "Invalid SQL query" acts like a blindfold; it reduces a 50-line script to a simple binary pass/fail. You are left staring at a wall of text, completely unable to determine if the failure is a missing parenthesis on line 2, a reserved keyword on line 18, or a malformed macro at the very end.
Furthermore, this generic output actively masks the true database error. The underlying PostgreSQL or ClickHouse engine is actually generating a highly detailed error code (such as "Data type mismatch," "Function does not exist," or "Division by zero"). However, the FortiAnalyzer GUI intercepts that detailed message and lazily translates all of them into the exact same "Check the syntax" warning. This forces you to abandon targeted troubleshooting and instead rely on a primitive "safemode" approach—manually deleting or commenting out halves of your query over and over until the error disappears, just to isolate the offending line.
Fortinet should be accountable for this, but I guess no one will bother replying or acknowledging this post as usual.
