Gotcha. Thanks so much!
Posts made by dqueubed
-
RE: not allowed to run insecure content from ... error
-
not allowed to run insecure content from ... error
We are running JS Report behind a reverse proxy that's doing our ssl offloading and trying to click into a subreport is throwing this error. How do we get beyond this?
As always, thanks so much. -
RE: HTML should reference our proxy servername instead of localHost
ACTUALLY ... hold on a moment. Just found where I call the url in my node.js script.
No need to respond again ... yet.
-
RE: HTML should reference our proxy servername instead of localHost
Also, this is how our config file begins ...
That looks correct, right?
-
RE: HTML should reference our proxy servername instead of localHost
@admin ... yes, we are linking to scripts and subreports.
My scenario is directly related to this playground example, and I'm uncertain where I explicitly call the POST - https://playground.jsreport.net/w/dqueubed/evJHTFm3
Can you pinpoint that for me please?
Thanks again for all your help. It's greatly appreciated.
-
HTML should reference our proxy servername instead of localHost
Hi all ... we have a production server that needs to render HTML and have the referring scripts properly pointing to our servername. Our proxy works fine (https://client.ourapp.net/reports), but when we render an html report that has links in it, the following is included in the output file. How do we change this to reference our proxy address above?
-
RE: onClick not firing <script> function
@bjrmatos ... you're absolutely right - I'm a promises n00b. My company has made it a "standard" to stay away from promises in lieu of using standard async functions. Those decisions are way beyond my paygrade and knowledge base. All that said, you've TOTALLY saved my biscuits here and I can't begin to thank you enough.
I believe I have everything I need, at least for now <fingerz_crossed> :-)
-
RE: onClick not firing <script> function
@bjrmatos ... this looks really promising, however, when I add the code to the master report the function doesn't run. I checked to see if I could find additional forum entries for report.toObjectURL() but couldn't find anything.
What does that do? What am I doing wrong? Thanks again!
-
RE: onClick not firing <script> function
@bjrmatos ... one more really quick question.
I can't find information on how to implement a BACK button for a sub/child report. I've tried just using an html button with history.back(), but that doesn't work. Any suggestions?
Thanks again!
-
RE: onClick not firing <script> function
Well .... THIS is embarrassing. I'm not familiar with the .then and .catch syntax and thought it was a part of the render function. My apologies for the rookie mistake and very much appreciate the quick assist. You guys are the best. Now, fingers crossed I can get my filtering to work <thumbs_up> Thanks again.
-
onClick not firing <script> function
Not sure what's going on, but for some reason the function inside my script tags is not firing in order for me to generate a filtered subreport (separate issue). Have tried several browsers, dumping cache, etc, but this seems to be "spotty" at best. Works sometimes, and doesn't at others.
Ideally, my script would perform some javascript to filter a dataset and pass those results to a subreport, but I can't seem to make that happen either because my function doesn't fire.
Any assistance is GREATLY appreciated, as always. Thanks much.
Playground: https://playground.jsreport.net/w/dqueubed/evJHTFm3
-
Using AWS S3 for template storage
What is the minimum version of JSReport required to utilize S3 for templates?
I have a new installation (v4.0) and when the server starts I see messages indicating fs store is persisting using aws-s3 and verifying bucket and SQS info. However, when I add the fs-store-aws-s3-persistence extension to an existing 3.13 server, then update my jsreport.config.json file to use S3, the server doesn't throw any errors upon startup, but it's also not connecting to S3. Thoughts?
Thanks as always.
-
RE: Chart.js - difficulty populating arrays from dataset
@jan_blaha ... just a quick follow up, this worked great
let customersArr = [{{#each smsMain.data}}"{{this.company}}",{{/each}}]; let customersDataArr = [{{#each smsMain.data}}{{this.deliveredCount}},{{/each}}];
As you can see, for the string array I had to force quotation marks and commas, but after that, everything worked great!
As always, you guys are right on the money with your solutions. Can't thank you guys enough, and I'm certain I'll have more. :-)
-
RE: Chart.js - difficulty populating arrays from dataset
Thanks @jan_blaha ... I'll pour over these and see what I can find. Always much appreciated :-)
-
Chart.js - difficulty populating arrays from dataset
Hi all ... I am trying to use chart.js in my report and am having difficulty populating the arrays for labels and data. Additionally, when I hard-code the arrays the chart runs, but not to completion.
I thought I could just use a handlebars
#each
statement to populate the arrays, but that doesn't appear to be the case, and examples of how to do this are sparse and don't appear to fit my use case, which is primarily doing this in the designer so I can just call the render from node. Seems a lot of examples are doing things like callinghandlebars.compile
and using JQuery ... not necessarily the solution I'm after unless it's the ONLY one.Here's a snippet of my code between the script tags
let customersArr = []; // let customersDataArr = [51, 325402, 524, 23565]; let customersDataArr = []; {{#each smsMain.data}} customersArr.push({{this.company}}); customersDataArr.push({{this.deliveredCount}}) {{/each}} new Chart("CustomerSummary", { type: "bar", data: {
Here is a link to my playground example - https://playground.jsreport.net/w/dqueubed/vkEiLVmu
As always, thanks for much for your assist!
- Roger
-
RE: Subreport - trying to call and run from main report
@bjrmatos ... great food for thought. We do indeed feed data to our reports dynamically and render from a script, but I'm always curious about options and other opportunities, so I may mess around with the browser-based method as well. In all instances, I am most appreciative of your help here. Thanks as always for your support ... you guys are awesome.
-
RE: Subreport - trying to call and run from main report
@bjrmatos ... <DOH>
Man ... I apologize. I didn't fully understand that you'd made adjustments in the playground :-( Anyway, indeed, I was able to copy and run the changes successfully.qq: is this how I need to do it moving forward? Or is there a patch/fix/alternative way I should look to do this going forward?
I know there are more people to support than just myself, and I genuinely appreciate you taking all this time with me. It's very much appreciated.
Thanks again, and let me know.
-
RE: Subreport - trying to call and run from main report
@bjrmatos ... ok, here are my 2 reports running locally in their entirety. From my main report (msub_rptMain) you can see I have the detail function coded with the template and datasource. Running msub_rptMain yields this ...
The subreport (msub_rptSub) looks like this when it's been run as a standalone, using msub_sub for a dataset.
However, clicking the "drill down" button from the main report doesn't actually run the report ... it simply yields the Amin string I have set to let me know if I'm (programmatically) in the right location.
I should be seeing the entire report being generated, right?
-
RE: Subreport - trying to call and run from main report
Thanks @bjrmatos ... trying this now.
-
RE: Subreport - trying to call and run from main report
@bjrmatos ... aaahhhh, ok gotcha. I guess that also explains why I can't seem to update my local version to 3.11 - tried a few times using online instrux but when I fire up JSReport is still says I'm on 3.9 <thumbs_up>. Also, in the video when you changed the recipe to HTML and the sub report ran only showing the text "Amin" ... I am indeed seeing THAT as well. Not rendering the results, but only showing the Amin response.
q: what do you need me to do here?
Happy to provide details, test, or ???? ... just let me know. As always, thanks so much ... very appreciative of your time and assistance. :-)