DayBackOnline

Jump To My Event

DayBackOnline.JumpToMyEvent History

Hide minor edits - Show changes to output

February 10, 2016, at 02:59 PM by Dan Wheelon - Removed note saying Custom Actions not yet supported
Changed line 3 from:
This is one of the things we designed [[custom actions]] to do. Those aren't online in DayBack Online yet but we hope to have them up and running soon.
to:
This is one of the things we designed [[custom actions]] to do. A custom action could be added that jumps over to the event's contact or project in FMP, FMGo or even in WebDirect.
July 03, 2015, at 07:59 PM by 142.4.217.187 -
Changed lines 1-13 from:
!! Can I Click a Button in the Calendar to See the Event in One of My Layouts?

Absolutely. =)

This
is most easily done with a custom action and DayBack comes with one such action already: "View Event Record". More info on using custom actions and modifying the "View Event Record" action here: [[Custom Actions]].

You can also configure DayBack to show your event directly in your own layout when you click in the calendar (instead of using one of the webviewer's popovers). Notes on how to do that can be found here: [[Your Own Event Layouts]].

!! What If the Event Layout I Want to Use is in Another File?

If you're configuring DayBack to show your event directly in your own layout (option 2 above) then that layout has to be in the same file as the calendar's webviewer layout (though the layout can certainly show records from another file).

If you'd like your custom action layout to reside in another file write a script in your file that can accept the event's ID as a parameter and call that script from DayBack's script "Go To Event Record From WebViewer". If you have multiple sources you may want to test for them in "Go To Event Record From WebViewer" and call your external script only when going to an event in that particular $source number
.
to:
!! Can I Click a Button in the Calendar to See the Event in My FileMaker File?

This is one of the things we designed [[custom actions]] to do. Those aren't online in DayBack Online yet but we hope to have them up and running soon.
Changed lines 1-3 from:
!! Can I click a button in the calendar to see the event in one of my layouts?

Absolutely.
to:
!! Can I Click a Button in the Calendar to See the Event in One of My Layouts?

Absolutely. =)
Changed lines 11-13 from:
%color=red% >> coming soon.
to:
If you're configuring DayBack to show your event directly in your own layout (option 2 above) then that layout has to be in the same file as the calendar's webviewer layout (though the layout can certainly show records from another file).

If you'd like your custom action layout to reside in another file write a script in your file that can accept the event's ID as a parameter and call that script from DayBack's script "Go To Event Record From WebViewer". If you have multiple sources you may want to test for them in "Go To Event Record From WebViewer" and call your external script only when going to an event in that particular $source number
.
Changed line 7 from:
You can also configure DayBack to show your event directly in your own layout when you click in the calendar (instead of using one of the webviewer's popovers). Notes on how to do that can be found here: [[Event Popovers]].
to:
You can also configure DayBack to show your event directly in your own layout when you click in the calendar (instead of using one of the webviewer's popovers). Notes on how to do that can be found here: [[Your Own Event Layouts]].
Changed lines 5-25 from:
When you click on an event in the calendar it comes up in the Event Details mini window. We already have a script written that will close this window and take you to the event record in another layout in your solution.

So add a button to the Event Details window, and add
the script "Jump to Event in My Layout ( Event ID )" to this button: add the field containing the primary key (unique ID) of your event as the script parameter. For example, this would be SampleEvents::_id in the sample events table that comes with the calendar.

Now edit the script "Jump to Event in My Layout ( Event ID )" and you'll see two areas that need you to modify them: the first specifies the layout you'd like to see you event in, and the second is a SetField that probably says Field Missing: you'll need to point that at the sample events field in your table so it looks something like this:

-> SetField [SampleEvents::_id; Get ( ScriptParameter )]

That's it!

Note that you may end up having one of these scripts for each [[multiple sources | source]] as each will have their own detail layout.

!! What if my layout is in another file?

If you want to see the event in a mini window first, and *then* jump to the layout in your file, you can use our script "Jump to Event in My Layout ( Event ID )" to call a script in your file, passing the event iD as a script parameter. The script in your file would then go to the right layout and perform a find for the eventID.

That is the easiest way.

If you want them to go right to the layout in your file when you first click on an event, you'll still write the same script in your file to find the event by event ID, but you'll call that script from within our script "Click in / Drag Event". If you have only one source in the calendar, you can replace everything between the comment "----------------  Else, display the selected record  ----------------" and the comment " > > End If Mixed Sources" with a call to the script in your file, the script parameter containing the event ID would be $sc_UID

If you have more than one source this is trickier, and we can build this for you as a custom modification
.
to:
This is most easily done with a custom action and DayBack comes with one such action already: "View Event Record". More info on using custom actions and modifying the "View Event Record" action here: [[Custom Actions]].

You can also configure DayBack to show
your event directly in your own layout when you click in the calendar (instead of using one of the webviewer's popovers). Notes on how to do that can be found here: [[Event Popovers]].

!! What If the Event Layout I Want to Use is in Another File?

%color=red% >> coming soon
.
August 07, 2010, at 12:38 AM by 76.22.123.157 -
Changed lines 15-25 from:
Note that you may end up having one of these scripts for each [[multiple sources | source]] as each will have their own detail layout.
to:
Note that you may end up having one of these scripts for each [[multiple sources | source]] as each will have their own detail layout.

!! What if my layout is in another file?

If you want to see the event in a mini window first, and *then* jump to the layout in your file, you can use our script "Jump to Event in My Layout ( Event ID )" to call a script in your file, passing the event iD as a script parameter. The script in your file would then go to the right layout and perform a find for the eventID.

That is the easiest way.

If you want them to go right to the layout in your file when you first click on an event, you'll still write the same script in your file to find the event by event ID, but you'll call that script from within our script "Click in / Drag Event". If you have only one source in the calendar, you can replace everything between the comment "----------------  Else, display the selected record  ----------------" and the comment " > > End If Mixed Sources" with a call to the script in your file, the script parameter containing the event ID would be $sc_UID

If you have more than one source this is trickier, and we can build this for you as a custom modification
.
July 22, 2010, at 04:34 AM by 76.22.123.157 -
Changed line 15 from:
Note that you may end up having one of these scripts or each [[multiple sources | source]] as each will have their own detail layout.
to:
Note that you may end up having one of these scripts for each [[multiple sources | source]] as each will have their own detail layout.
February 03, 2010, at 03:36 PM by 76.22.123.157 -
Changed lines 13-15 from:
That's it.
to:
That's it!

Note that you may end up having one of these scripts or each [[multiple sources | source]] as each will have their own detail layout
.
February 03, 2010, at 04:30 AM by 76.22.123.157 -
Changed lines 11-12 from:
SetField [SampleEvents::_id; Get ( ScriptParameter )]
to:
-> SetField [SampleEvents::_id; Get ( ScriptParameter )]
January 20, 2010, at 02:07 AM by 76.22.123.157 -
Added lines 1-13:
!! Can I click a button in the calendar to see the event in one of my layouts?

Absolutely.

When you click on an event in the calendar it comes up in the Event Details mini window. We already have a script written that will close this window and take you to the event record in another layout in your solution.

So add a button to the Event Details window, and add the script "Jump to Event in My Layout ( Event ID )" to this button: add the field containing the primary key (unique ID) of your event as the script parameter. For example, this would be SampleEvents::_id in the sample events table that comes with the calendar.

Now edit the script "Jump to Event in My Layout ( Event ID )" and you'll see two areas that need you to modify them: the first specifies the layout you'd like to see you event in, and the second is a SetField that probably says Field Missing: you'll need to point that at the sample events field in your table so it looks something like this:

SetField [SampleEvents::_id; Get ( ScriptParameter )]

That's it.
(855) SEEDCODE
[email protected]
Follow us: