Forum Replies Created
-
AuthorPosts
-
You don’t show the data viewer, but you say it’s$event type open.
Did you follow the the steps above?
-
Please also confirm that the calendar is “Client Side Scripting” and whether you’re server-powered or standalone.
Thanks
-
The data viewer doesn’t always update quickly enough unless you’re paused in script debugger. If my suggestions above don’t work, try running Script Debugger and making sure all the variables are set as soon as the script starts running.
-
The action script that runs is completely editable. We provide a sample in our soSIMPLE Calendar starter file.
You can step through the script to see where it’s not doing what you want it to do.
If you haven’t customized your script, sometimes what happens is you change layouts or field names in your data source without making the same changes in the first few lines of your action script. If this is the problem, follow these steps:
- Open soSIMPLE Calendar Settings file
- Select the calendar that you’re working with. Verify the data source settings.
- Click “Use in FileMaker Pro/Go”
- Click “Copy just the variable steps”.
- Now go back to your action script, select the 3 “set variable” steps at the top of the script, remove them and choose “paste”
This will update the layouts and field names with the choices you made in the settings file.
-
Unfortunately, that timeout is tied to FileMaker’s API. We haven’t had much success changing the timeout. Perhaps you could separate your feed into batches by filtering the feed with URL filters?
-
This reply has been marked as private.
-
It’s likely just a time-out issue. We usually try to limit the iCal feed data source to only include the past 60 days or so as most clients just need to see current information. We do this by creating a calculation field in the events table and mapping it to the “display only flag” field in the data source. The calculation could be something like “if (start date > get(currentdate) – 60; 1)”.
-
Hi Günter –
Can you tell me if something changed to cause this problem, or is this a new installation?
Are you working standalone or server powered?
Do you have “Client-Side Script” selected for this calendar?
For tablets, you must turn on the “Touch Enhancements” option in soSIMPLE Calendar Settings (click “Edit” next to “Options” for your calendar).
While you’re in “Options” also make sure that “Read Only” is not enabled.
Assuming you’re using client-side scripting &/or standalone mode:
If you’re using FileMaker Pro Advanced, you can turn on your Script Debugger to make sure the Action Script is running. Every time you do anything in your calendar, the Action Script runs and several variables are set. Can you tell me if that script is running? If it is, make sure the $event_type variable is set to “edit”, “open”, or “new”. If you don’t have FileMaker Pro Advanced, you can add a “Show Custom Dialog” to the first step of that script to tell you what that variable is set to. Set the text of the dialog to “Current edit mode is ” & $event_type.
If the script isn’t running at all, it’s likely that FMPA17 didn’t install the fmp:// protocol properly. You can fix that here:
-
Hi there William –
Just a couple of follow-up questions to help narrow this down:
- Are you using “Client Side Scripting” as your calendar method?
- Are you working within FileMaker Pro (not WebDirect, or other app)?
- Do you have an “Advanced Find Script” set in your data source settings? What do you used Advanced Find to do?
- Do you have a custom code (“Custom JS”) that we created for you?
Thanks
-
Thank you William.
Are you receiving this message in the Calendar’s web viewer? Or when a new person tries to log in? Or getting them back from PSOS calls?
I do not believe that’s related to soSIMPLE and definitely does not have to do with licensing – any time I’ve seen the 812 error, it’s coming from script sessions on the FileMaker Server (either from PSOS or Scheduled Scripts). Have you adjusted the number of scripts that can be run on the server console?
https://community.filemaker.com/thread/189639
-
That’s not built in, but we can certainly add as a custom dev project. Let me know if you’re interested, and we can give you an estimate.
Thanks
-
Hi William –
While there is no option to modify this within the configuration, you can add the following into your Custom JS area in the settings file:
scheduler.config.map_initial_position = new google.maps.LatLng(48.724, 8.215);
Replace the two numbers in parenthesis with the Latitude and Longitude that you’d like to start.
Instructions for adding this code:
Add custom code to soSIMPLE Calendar
Let us know how it goes.
-
Make sure you’ve followed the installation instructions here:https://www.sosimplesoftware.
com/products/calendar- documentation/calendar- builder-reference/calendar- modes/how-server-powered- works/installing/ The basic steps of installation:- Turn on PHP services on your FileMaker Server
- Put the folder called “sosimple” (which contains php code) in your web folder.
- Upload the soSIMPLE fmp files to your server
- Open soSIMPLE Calendar Settings from your computer.
The message you’re seeing could be due to #1 or #2 above. Please also make sure that the “Master Machine” toggle is turned on. It’s on the Connector tab in the admin console.Let me know if that helps. -
Yes. FileMaker 17 does not always properly register the “FMP” url protocol when it’s installed. Follow these instructions to fix this issue:
https://www.sosimplesoftware.com/forums/topic/action-script-not-performing-blank-web-viewer/
-
Hi Richard.
Have followed the installation instructions included in the download? It sounds like one of these three issues:
- you haven’t installed the sosimple php directory
- you haven’t turned on php web publishing on the filemaker server
- you put the sosimple php directory in the wrong location.
Please review these instructions and confirm you put the files in the right place.
Thanks
-
Hi Michael –
There have only been a couple of request for this so far. We’re certainly looking into next steps for this App, and that would probably one of the first most likely ones.
Thanks
Ken
-
Hi Clive –
Sorry you’re running into trouble.
You’re using Server-Powered, correct?
Are you using the Starter file (called “soSIMPLE Calendar”) or your own integration?
When you say no data is showing in the web viewer, do you mean no dates are showing, or the calendar grid isn’t showing either?
Thanks.
-
You’re absolutely right, Andre.
The sort occurs first by date/time, then by id. So you can change your ID, if that is possible. Using custom development, we can also change the sort order by another field.
When you say “size of each resource row could be fixed,” do you mean that in timeline view, each resource row should be set to a certain height? Right now each resource row is the same size and is set to dynamically fill the screen. You’d prefer, for example, for all rows to be 100px high – the result being a large white space at the bottom of the timeline, on large monitors with few resources, and always needing to scroll on small monitors with many resources? We can accomplish this with custom code if you’d like.
-
The easiest way to do this is to implement an Advanced Find script and perform a sort in that script before returning the results.
An Advanced Find script is essentially a server-side script that get run right after events are pulled from the server. Since the events have already been “found” when this script is run, all you should have to do is have a single step in that script that performs a sort. The script doesn’t actually need to perform the find itself.
- Create a script in your FileMaker file.
- Add only a sort step to that script, sorting the way you’d like it. It will run in the context of your found set of appointments.
- In the Settings file, edit the Data Source for your custom calendar.
- In the Data Source window, select the script you created next to “Advanced Find script”.
Let us know how it goes.
Thanks
-
Hi Andre. I’m afraid the attachment did not come through.
-
Hi Rich –
Ultimately, you want the URL to end with #mode=unit
If you’re using your own custom app, you may be setting the URL via script, or using a calculation.
If you’re using the soSIMPLE Calendar starter file, that value is set in the Setup Calendar & Refresh Calendar scripts. You can just append it to the “Set Web viewer” step.
-
Your pasted image didn’t come through. I imagine you’re seeing MBS’s popup? See here:
-
Hi Marianne!
Unfortunately, there’s no way to know if anyone’s subscribed over iCal.
However, the way that iCal subscriptions usually work, the events are cached on each persons calendar (like Apple Calendar, Google Calendar, Outlook) then periodically updated. If you remove files from the server or turn off FileMaker server, people will still have the events they’ve received and will sync again the next time it’s available.
-
Hi Andy,
Are you sure you’re following the right video? PHP rights is at timestamp 3:22 in the video for Server-Side integration.
Confirm that you’re following the right instructions as standalone is completely different. Make sure you’ve also installed soSIMPLE software on your server and tested the installation where the instructions suggest.
The second issue you’re having is actually two issues –
1. The default for FMP is not always set properly by the FileMaker 17 installer, which is why you’re launching FMP16 by accident. Here’s more details with a fix for that issue:
https://www.sosimplesoftware.com/forums/topic/action-script-not-performing-blank-web-viewer/2. The user working in your app must have FMURLSCRIPT privilege set. See more information here:
https://www.sosimplesoftware.com/sosimple-help/using-your-sosimple-calendar-with-filemaker-16/This is mentioned on the integration instructions page, but not in the video itself.
-
Thanks for the details. I don’t think it will be an issue to have a related field in the Data Source so long as extended privileges are set right for that table & field. We’ll confirm that here.
Have you entered a Google API key into soSIMPLE Calendar Settings file? It’s possible that if that has not yet been entered, that may cause a problem when Google attempts to map that field.
A good way to check is to see if a local field shows the same issue when mapped to the “Event Location”
-
AuthorPosts