![]() If you don't see a login page, then your network is blocking the domain: ask your IT department to "whitelist", and you'll be all set. To double-check, try and open in your browser. This is likely because your network is blocking the domain. Information on how to do this can be found here under "Authorizing Users."Īll I see is a frowny face on the DayBack tab in my org To fix this, you can change the Connected App settings to pre-authorize by profile, and that will bypass the authorization step. If you are a system admin, Salesforce might just be getting confused between your single-sign-on and sandbox logins. If you're logged in a less than a system administrator, it may be that your user privileges don't include authorizing new apps: you'll want to ask a system administrator for help. If that's the case, here's how to delete that unnecessary calendar: But it also comes up if you've accidentally created a new calendar. In that case, finish your field mapping and the error will go away. This error can show up if you've left DayBack's field mapping incomplete when you're setting up a new calendar. I see a red "Malformed Query Object" at the bottom of the screen For now, if you need DayBack to be more zoomed in, a workaround is to adjust your system-wide scaling or use a different browser (Safari, Firefox). We'll try to address this in a future update to DayBack. Unfortunately, these browsers don't always zoom table headers the same as the table body, so this can cause the header to be zoomed disproportionately to the calendar rows. This can happen if your browser is zoomed in or out (not at 100% zoom) in a Chromium-based browser (Chrome, the new Edge). The column headers in resource pivot views don't line up with the columns Update to the latest version of FileMaker and you should be all set. FileMaker users on Windows need to have FileMaker 19.3.1 or later to use DayBack. This is because you're using an older version of FileMaker for Windows. I see "DayBack is Loading" on my Windows machine. ![]() If you enter 06:07:00, you'll see odd results. Visit "Time Scales" in the left-hand sidebar of Admin Settings, and you've likely entered an odd time into one of the settings like "earliest time visible." These values should be in the form HH:MM:SS like 06:00:00 for 6am. Times down the left-hand side are all random, like 10:08 If that's set to NO and your action is using () you're essentially telling DayBack to render the calendar twice. If you've created any App Actions, check that the action's "Prevent Default Action" is set correctly. ![]() Salesforce and FileMaker data sources have a lot of options, though, so you'll see common issues for those sources below. Note, there isn't much to set up for Google or Basecamp sources, so not much can go wrong. If you like getting your hands dirty and would like to dig into this yourself, we hope the following walkthroughs will help. If something doesn't look right, please get in touch.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |