855.367.3511 | CONTACT US

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - taniac

Pages: [1] 2 3 ... 10
1
Support Questions / Re: Report Viewing
« on: May 17, 2017, 02:09:43 pm »
Unfortunately Microsoft does not support rendering extensions to the rdlc control, only the server.  You can use SSRS Express.

2
Release Updates / Re: V6 Release - January 2017
« on: January 31, 2017, 03:48:43 pm »
We have released build 6.0.376.0 to the support site. This build includes the following fixes and enhancements:

  • Updates have been made to the report viewer page
  • Added ISV comment
  • Added report viewer page
  • Update registration and ordering for new viewer control (full and standard) which the customer can now purchase from the website for a 1 year subscription
  • Update to support if more than one version running on same DB
  • Change date time to allow time
  • fix back on cascading tree to no longer have a validation error
  • fix zoom tooltip
  • fix case with hidden parameter in cascading tree
  • Fixed setup to always overwrite files

3
Support Questions / Re: Using with MVC bundle. Javascript error.
« on: January 25, 2017, 06:16:43 pm »
We have released new NuGet files for build 6.0.373.0. We have included fixes for your issue in this build.

4
Support Questions / Re: Report issues in iOS 10
« on: January 13, 2017, 06:44:12 am »
Sorry about the confusion.  In the latest build we made the async processing off by default to minimize the change to other customers.  To turn this on please add the following to your web.config.

<add key="Forerunner.EnableAsyncRendering" value="true"/>

5
Support Questions / Re: Report issues in iOS 10
« on: January 13, 2017, 06:41:45 am »
There is an issue with iOS 10 and we have a work around. It will be addressed in the next build.

6
Support Questions / Re: Report issues in iOS 10
« on: January 13, 2017, 06:34:35 am »
After reviewing the log files that were sent to us it appears to be a timeout issue. The mobilizer timeout is in the Web.config file.  The default is

<add key="Forerunner.ReportServerTimeout" value="100000" />

Or 100 sec.  Please increase this value.
 

7
Release Updates / V6 Release - January 2017
« on: January 09, 2017, 02:36:00 pm »
We have released build 6.0.356.0 with the following enhancements and bug fixes:

  • Login will not fail after clicking twice with no credentials
  • Updated date logic for loc dates and valid values
  • Added support for sortable columns in explorer list view
  • Added tooltips for explorer items

8
Release Updates / V4 Release - January 2017
« on: January 09, 2017, 02:30:11 pm »
We have release build 4.0.472.0 to the support site with the following changes:

  • Resolved issues with date logic, specifically around valid values
  • Last page device info will no longer have issues

9
Release Updates / V6 release - December 2016
« on: December 16, 2016, 07:07:32 am »
We have released build 6.0.330.0 today. We have added the following to this build:

  • .net 4.5.2 requirement
  • support for basic thumbnails and authentication
  • fixed tool tips on action
  • when there is not a user setting in dev viewer mode reports will work
  • Added support for Async report processing, fixes apple timeout bug
  • improved tool tips for cascading parameters
  • improvements to parameters

10
Support Questions / Mobilizer support for SSRS mobile reports
« on: September 15, 2016, 01:49:55 pm »
We have released the update that now support SSRS Mobile reports in Mobilizer.

To configure:
Add the following setting to the MobilizerSettings .txt in the custom folder.
"SSRSMobileReportsURL":"http://YourSSRSServer/Reports"

And add the following setting to your web.config
<add key="Forerunner.EnableSSRSMobileReports" value="True" />

11
Release Updates / V6 release - September 2016
« on: September 14, 2016, 02:58:39 pm »
We have released build 6.0.217.0 to the Support site. The following changes are included in the build:

  • Support for SSRS 2016 mobile reports

12
Coding Questions / Re: Support - App/Server Split
« on: July 27, 2016, 01:19:04 pm »
It can be done in many ways.  You can either run Mobilizer as a standalone app as you are doing.  You can run it in an app of your own using the SDK.  Both of these options has the client as server code in the same domain. 

If you want to have the client code in one app and the server code in another app you can do that to but you need to setup CORS.

This setup is more complicated and but several of our customers are doing it.  The complication is ASP.Net not mobilizer.  Mobilizer has just one setting you need to set.

Mobilizer will determine the API location from the load path of the js files.
For example <script type="text/javascript" src="http://hTTP://MyMobilizerServer/Mobilizer/Forerunner/Bundles/forerunner.min.js"></script>


If your client code is on a different domain then your need to enable CORS to make cross domain calls.

To do this for Mobilizer you need to set the following setting in your web.config that is hosting the server API.  If using mobilizer this is the mobilizer web.config
You need to tell Mobilizer it can trust a different domain.

<httpProtocol>
      <customHeaders>
        <clear />
        <add name="Access-Control-Allow-Origin" value="http://localhost:1337" />
        <add name="Access-Control-Allow-Credentials" value="true" />
        <add name="Access-Control-Allow-Methods" value="GET, POST" />
        <add name="Access-Control-Allow-Headers" value="Content-Type, *" />
       
      </customHeaders>

</httpProtocol>


If you want to pass credentials then you need to also set a header on the client before making ajax calls
For Mobilizer you simply need to set before creating any forerunner objects.

forerunner.config.enableCORSWithCredentials = true;

13
Support Questions / Re: Using the ReportViewer
« on: June 07, 2016, 10:05:35 am »
The Forerunner.ReportServerWSUrl must point at the SSRS webserver end point,  It is usually http://someserver/reportserver

Assuming your install of Mobilizer works, it is the value you put in the config tool when you setup mobilizer.

Since you are setting the credentials to SSRS in the controller it does not matter what authentication you use for your app.

14
Support Questions / Re: Using the ReportViewer
« on: June 07, 2016, 09:51:24 am »
The login prompt is from your application.  The Report Manger controller expects the requests to be authorized, so your application will need to authentic in some way.  This is different than the credentials needed to talk to SSRS.  If you want your application to unauthenticated, you can remove the  [Authorize] tag from the Report Manager and Report Viewer controllers.

It also looks like your <add key="Forerunner.ReportServerWSUrl" value="http://devappserver.staplescan.com/Mobilizer" />  setting is incorrect.  Usually this would end with /reportServer for the API endpoint.

15
Support Questions / Re: Help resetting license
« on: March 08, 2016, 11:32:59 am »
We have the ability for you to get info on your key.  We cannot let you reset a key, as that would essentially invalidate our licensing model.

For example, using your key.
https://forerunnersw.com/register/api/license/info?Key=m9WkdA

Pages: [1] 2 3 ... 10