Drag To Duplicate
DayBackForFileMaker.DragToDuplicate History
Hide minor edits - Show changes to output
Changed lines 13-15 from:
-> • {-If your calendar source is set up to [[YourOwnEventLayouts | edit your events in a FileMaker layout]], instead of in DayBack's popover, the duplicate doesn't yet work: it just creates a new event. We should be able to get this working in a future in-app update.-} Released in build 9.97!
-> • This doesn't do the same thing as duplicating a FileMaker record using FileMaker's dupe command. It really creates a new FileMaker record with the same DayBack information as the original. This means that unmapped fields (fields in your table but not mapped to DayBack edit fields) are not duplicated into the new event.
->
to:
-> {-If your calendar source is set up to [[YourOwnEventLayouts | edit your events in a FileMaker layout]], instead of in DayBack's popover, the duplicate doesn't yet work: it just creates a new event. We should be able to get this working in a future in-app update.-} Released in build 9.97!
-> This doesn't do the same thing as duplicating a FileMaker record using FileMaker's dupe command. It really creates a new FileMaker record with the same DayBack information as the original. This means that unmapped fields (fields in your table but not mapped to DayBack edit fields) are not duplicated into the new event.
-> This doesn't do the same thing as duplicating a FileMaker record using FileMaker's dupe command. It really creates a new FileMaker record with the same DayBack information as the original. This means that unmapped fields (fields in your table but not mapped to DayBack edit fields) are not duplicated into the new event.
Changed lines 13-16 from:
-> � {-If your calendar source is set up to [[YourOwnEventLayouts | edit your events in a FileMaker layout]], instead of in DayBack's popover, the duplicate doesn't yet work: it just creates a new event. We should be able to get this working in a future in-app update.-} Released in build 9.97!
->� This doesn't do the same thing as duplicating a FileMaker record using FileMaker's dupe command. It really creates a new FileMaker record with the same DayBack information as the original. This means that unmapped fields (fields in your table but not mapped to DayBack edit fields) are not duplicated into the new event.
->
to:
-> • {-If your calendar source is set up to [[YourOwnEventLayouts | edit your events in a FileMaker layout]], instead of in DayBack's popover, the duplicate doesn't yet work: it just creates a new event. We should be able to get this working in a future in-app update.-} Released in build 9.97!
-> • This doesn't do the same thing as duplicating a FileMaker record using FileMaker's dupe command. It really creates a new FileMaker record with the same DayBack information as the original. This means that unmapped fields (fields in your table but not mapped to DayBack edit fields) are not duplicated into the new event.
-> • This doesn't do the same thing as duplicating a FileMaker record using FileMaker's dupe command. It really creates a new FileMaker record with the same DayBack information as the original. This means that unmapped fields (fields in your table but not mapped to DayBack edit fields) are not duplicated into the new event.
Changed line 21 from:
To enable the feature in your copy of DayBack, just click Admin Settings on the Settings tab of the left-hand sidebar and the click "Check for Updates". This is a free, [[InAppUpdates | in-app update]]. Enjoy!
to:
To enable the feature in your copy of DayBack, just click Admin Settings on the Settings tab of the left-hand sidebar and then click "Check for Updates". This is a free, [[InAppUpdates | in-app update]]. Enjoy!
Changed lines 5-6 from:
%newwin% [[https://youtu.be/jBS6i6hBiQg]]
to:
%newwin% [[https://youtu.be/jBS6i6hBiQg]]
Changed line 21 from:
To enable the feature in your copy pf DayBack, just click Admin Settings on the Settings tab of the left-hand sidebar and the click "Check for Updates". This is a free, in-app update. Enjoy!
to:
To enable the feature in your copy of DayBack, just click Admin Settings on the Settings tab of the left-hand sidebar and the click "Check for Updates". This is a free, [[InAppUpdates | in-app update]]. Enjoy!
Added lines 16-17:
-> Any [[additional fields]] '''are''' duplicated, so you can make sure critical fields get duplicated by mapping them as additional fields. If you really want to duplicate the whole record yourself, you can store the event's original ID in a new field, map ''that'' as an additional field, and then pick up the id in your own script to set fields from the original record into the newly "duplicated" record. Please get in touch if that sounds tricky.
June 07, 2017, at 08:54 PM
by - Duplicate while using FM layouts implemented
Changed line 13 from:
-> � If your calendar source is set up to [[YourOwnEventLayouts | edit your events in a FileMaker layout]], instead of in DayBack's popover, the duplicate doesn't yet work: it just creates a new event. We should be able to get this working in a future in-app update.
to:
-> � {-If your calendar source is set up to [[YourOwnEventLayouts | edit your events in a FileMaker layout]], instead of in DayBack's popover, the duplicate doesn't yet work: it just creates a new event. We should be able to get this working in a future in-app update.-} Released in build 9.97!
Changed line 13 from:
-> � This does't do the same thing as duplicating a FileMaker record using FileMaker's dupe command. It really creates a new FileMaker record with the same DayBack information as the original. This means that unmapped fields (fields in your table but not mapped to DayBack edit fields) are not duplicated into the new event.
to:
-> � This doesn't do the same thing as duplicating a FileMaker record using FileMaker's dupe command. It really creates a new FileMaker record with the same DayBack information as the original. This means that unmapped fields (fields in your table but not mapped to DayBack edit fields) are not duplicated into the new event.
Added lines 1-2:
!! Easily duplicate event on the calendar
Changed lines 11-14 from:
to:
-> � If your calendar source is set up to [[YourOwnEventLayouts | edit your events in a FileMaker layout]], instead of in DayBack's popover, the duplicate doesn't yet work: it just creates a new event. We should be able to get this working in a future in-app update.
-> � This does't do the same thing as duplicating a FileMaker record using FileMaker's dupe command. It really creates a new FileMaker record with the same DayBack information as the original. This means that unmapped fields (fields in your table but not mapped to DayBack edit fields) are not duplicated into the new event.
!! How do I get it?
To enable the feature in your copy pf DayBack, just click Admin Settings on the Settings tab of the left-hand sidebar and the click "Check for Updates". This is a free, in-app update. Enjoy!
-> � This does't do the same thing as duplicating a FileMaker record using FileMaker's dupe command. It really creates a new FileMaker record with the same DayBack information as the original. This means that unmapped fields (fields in your table but not mapped to DayBack edit fields) are not duplicated into the new event.
!! How do I get it?
To enable the feature in your copy pf DayBack, just click Admin Settings on the Settings tab of the left-hand sidebar and the click "Check for Updates". This is a free, in-app update. Enjoy!
Added lines 1-12:
With [[Version History | version]] 9.85 you can now duplicate events on the calendar just by dragging them:
(:youtube jBS6i6hBiQg width=500:)
Hold down the option key (Mac) or the control key (Windows) ''before'' you click on your event and start dragging. You'll have the opportunity to edit your newly duplicated event before you save it.
A couple notes about this feature:
# If your calendar source is set up to [[YourOwnEventLayouts | edit your events in a FileMaker layout]], instead of in DayBack's popover, the duplicate doesn't yet work: it just creates a new event. We should be able to get this working in a future in-app update.
# This does't do the same thing as duplicating a FileMaker record using FileMaker's dupe command. It really creates a new FileMaker record with the same DayBack information as the original. This means that unmapped fields (fields in your table but not mapped to DayBack edit fields) are not duplicated into the new event.
(:youtube jBS6i6hBiQg width=500:)
Hold down the option key (Mac) or the control key (Windows) ''before'' you click on your event and start dragging. You'll have the opportunity to edit your newly duplicated event before you save it.
A couple notes about this feature:
# If your calendar source is set up to [[YourOwnEventLayouts | edit your events in a FileMaker layout]], instead of in DayBack's popover, the duplicate doesn't yet work: it just creates a new event. We should be able to get this working in a future in-app update.
# This does't do the same thing as duplicating a FileMaker record using FileMaker's dupe command. It really creates a new FileMaker record with the same DayBack information as the original. This means that unmapped fields (fields in your table but not mapped to DayBack edit fields) are not duplicated into the new event.
