Jump to content

ryan360Works

360Works
  • Content Count

    682
  • Joined

  • Last visited

  • Days Won

    22

ryan360Works last won the day on April 17

ryan360Works had the most liked content!

Community Reputation

42 Excellent

2 Followers

About ryan360Works

  • Rank
    360Works Support

Profile Information

  • Gender
    Not Telling

FileMaker Experience

  • Skill Level
    Expert
  • FM Application
    17

Platform Environment

  • OS Platform
    Mac
  • OS Version
    High Sierra

Recent Profile Visitors

6,660 profile views
  1. Hello, 1. Im not sure why you are getting those cells. I suspect it may have to with the fact that writing to non-existent table cells will create new rows/columns as needed. Perhaps the calculation that you have for the cell address is returning unexpected results. 2. Scribe cannot modify pre-existing text in a field. It will overwrite whatever is there so if you want a slash in between those two words you would need to pass that literal string in as the "value" parameter in ScribeDocWriteValue 3. Same deal as number 2, Scribe will overwrite whatever is in that cell with whatever value you put in for the "value" parameter in the ScribeDocWriteValue function call so you would need to pass in "NADIS" into the function call.
  2. Hi Cable, The dollarAmount in CCProcessAuthorizedPayment needs to be less than or equal to the chargeAmount passed into CCProcessPayment. edit: A bit more clarification, this is imposed at the gateway level so it may be that your gateway will allow the dollarAmount to be higher than the chargeAmount however it is usually the case that it needs to be less than or equal to. I would check with your gateway to see what they allow.
  3. Hi DataCruncher, The only time the server side plugin would be involved would be if you run a script with the Perform Script on Server script step or run said script as a schedule. Otherwise plugin functions are run locally.
  4. Hello, The Cloud versions in the current downloads are not meant for FMS Linux. We are still in development for these plugins. I do not have a timeline for when this development will be complete but we are aiming to have them ready prior to the official release. We will announce compatibility in our newsletter as well as on our social media accounts so be sure to subscribe to those so you will know when they are compatible.
  5. Hello, All of our plugins are 19 compatible. Can elaborate on the issue? Are you getting any errors? If the plugin will not enable it is typically due to issues with the JRE the plugin needs to operate. Please follow the instructions here to manually install it. If the plugin will still not enable please see the instruction here to find the initialization logs. You can email those to support@360works.com and reference this thread in your email.
  6. Unless there is an error being recorded I am not sure if the logs files will be helpful. That being said, plugin log file locations can be found here. As a test, you can remove the plugin from the equation by sending the GET request through a browser like <URL to file>?md5=true Check and make sure you get response headers after sending the request. In Chrome, go to View->Developer ->Developer Tools, Select Network, send the request, select it in the list and then click headers and make sure you got the response. If the issue is with the plugin I would suspect that the responses should take the same time on both machines. Alternatively, if you are familiar with how to use cURL in terminal/CMD you can do the same test.
  7. Hi AndyN, In order to troubleshoot, we will need to see the plugin logs. Please be sure to reproduce the issue you are seeing and then send the logs to support@360works.com before any restarts of FileMaker as restarting will overwrite the logs . This will create a support case for you in our support system. You can reference this thread in the body of the email. Please see this page for log locations.
  8. Hello, Those log files are used in the Reset/Rebuild sync data functionality. They can be deleted but you will no longer be able to use this function if something goes wrong. I would highly recommend that you leave them. That being said, if you are worried about the number of logs, consider upgrading to MirrorSync 6 as it writes less logs.
  9. It may be the file name is throwing something off with the path to the file. I would be happy to take a look at the logs. Make sure to add "LoggingLevel=DEBUG" to the connect function and then reproduce the issue. Once you have, you can send them in to support@360works.com and I will take a look. See this page for log locations.
  10. You may need to also modify the httpd-proxy-fmiwebd.conf file. See instructions here
  11. indeed you would use that button to add to any existing MirrorSync license
  12. Hi Glorifindal, This is definitely possible and is a common use case for a failover server in case there is an issue with the other server. You will need another Server to Server configuration in order to do so. If your license does not already have another one, you can purchase and add that configuration to your current license by going to the MirrorSync product page here and clicking on the button that says Pricing/Buy/Upgrade and then on the button that says "add to existing MirrorSync 6 license" (this will work for any MirrorSync license) and then entering in your license information into the respective fields. Please let us know if you have any questions!
  13. Hello, Judging from the error in your screen shot, it looks like you are using FMCloud 2 and MS 6. If you are looking at the documentation here, you may have missed the note about this only being necessary for MirrorSync 5 or earlier. This is also only applicable with FMCloud 1.XX as you can manage the ports in the AWS console where the EC2 instance would run. MirrorSync 5 or earlier is not compatible with FileMaker Cloud 2. If you are using FMCloud 2 and MS 6, please download and install this version of MS 6 as it has several improvements in regards to FMCloud 2. I believe this should clear the error in pic 4.
  14. Every SCGetInfo call is a GET request to the SuperContainer server as well as that being in an unstored calc is probably causing the calc to execute several times unnecessarily plus if 250K records are being checked, that's a lot of overhead. How are files being uploaded? via the plugin or a web viewer/browser? If through the plugin, I would just call SCGetInfo as part of the upload process and record that information in a field somewhere. That way you can just check for a value in a field rather than trying to hit the SuperContainer server every time. If you are not uploading via the companion plugin, it might get a bit tricky to do so.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.