![]() ![]() The first addition to the Fishbowl for Salesforce Application was the Shipment Export, which is a one-way sync designed to export shipment details from Fishbowl to Salesforce.Īfter an Opportunity is created in Salesforce and imported into Fishbowl as a Sales Order, via the Salesforce Order Import, the standard Fishbowl procedure is followed to pick, pack, and ship the order. This blog series will highlight some of the added functionality that you’ll find in the application today. Since the release of Fishbowl for Salesforce, we have added several new features to enhance and expand the capabilities of the application. You’ll need to contact Fishbowl support for further assistance. If you still receive the error, or you are not a FishBooks pro customer running FishNet, there is likely another task (such as a database backup or Quickbooks export) that is not functioning. ![]() Please contact us for assistance upgrading your FishSnap plugin! *Note that if your company also uses FishSnap, both the FishNet and FishSnap plugins will need to be updated for 2015. ![]() Simply contact FishBooks for installation instructions. Fixing the error requires a one-time reinstallation on your Fishbowl server. If you already reinstalled FishNet in preparation for your upgrade (we applaud your preparedness!), there is a chance that the FishNet files were deleted or lost from your Plugins folder during the upgrade, which would also cause this error. If you are a current FishBooks Pro customer, it is likely that your FishNet plugin needs to be reinstalled with 2015 compatible files. This error is usually caused by a task in your schedule module that is stuck or incapable of running. If you have recently upgraded to Fishbowl 2015, you may be seeing this persistent error when changing modules: Updating to Fishbowl 2015.0: Planning for Installation and Recoveryįishbowl 2015.0 | Will my reports run faster?įishbowl 2015 | Custom Report Compatibility Check Run the report again to ensure the error has been resolved! More helpful articles concerning the 2015 upgrade: *If a Custom folder already exists, simply copy and paste the contents of Custom folder from the old file path to the new Custom folder, instead of the folder itself 6. The default path for 64 bit Fishbowl is: C:\Program Files\Fishbowl\server\reports 5. Now, locate the “reports” folder for Fishbowl 2015 Go back one level to “reports” and copy the entire “Custom” folderĤ. When you have located the “Custom” folder, click into it to verify that your custom files are there. “C” and “D”are the most common, however your company may have Fishbowl on another drive, so adjust the file path accordingly. *The letter at the beginning of the file path represents the drive on which Fishbowl is located within the server. The default path for a 32 bit Fishbowl is as follows: C:\Program Files (x86)\Fishbowl\server\reports\Custom This error tells us that Fishbowl cannot locate the files it needs to run this report because the file path to the “Custom” folder has changed. To fix this, you will need to bring the Custom folder over to the new Fishbowl file path.įor this example, we will use the 32 to 64 bit conversion scenario, where Fishbowl has moved from Program Files (x86) to Program Files 1. In Fishbowl, the error will look like this: C:\Program Files\Fishbowl\server\reports\Custom\Name-Of-Report-File.jasperĪt .(LogicReport.java:786)Īt .(LogicReport.java:779)Īt .(LogicReport.java:670)Īt .(LogicReport.java:703)Īt .(LogicReport.java:129)Īt .ReportModule.getReport(ReportModule.java:82)Īt 0(Native Method)Īt (NativeMethodAccessorImpl.java:57)Īt (DelegatingMethodAccessorImpl.java:43)Īt .invoke(Method.java:606)Īt .EVEModule.handleEvent(EVEModule.java:189)Īt .handleEvent(MessageHandler.java:156)Īt .run(MessageHandler.java:115) C:\Program Files\Fishbowl\server\reports\Custom\Name-Of-Report-File.jasperĬom.: Report not found. If this was not done correctly, you will likely get the following error when you try to run a custom report: Error: ![]() In either case, it will be necessary to copy your Custom report files to the new Fishbowl file path. The Fishbowl file path may also change during the upgrade if your company created a new folder within Program Files for the 2015 version, so as not to override your existing 2014 data. This typically occurs when a company upgrades from running 32 bit to 64 bit, because Fishbowl moves from Program Files (x86) to Program Files. One such error, seen below, is triggered if the Fishbowl file path changes during the upgrade process, but the Custom report folder is not copied to the new path. If you have not yet upgraded to Fishbowl 2015, we recommend taking these precautionary steps to avoid the common errors that may occur when upgrading your Fishbowl version. Based on our interaction with Fishbowl customers throughout the release of the 2015 version, we have noticed certain errors that are frequently encountered during or immediately after the upgrade process. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |