Schedule changes when assets are moved, deleted, or renamed

When you move, copy, or delete assets in the asset tree, the schedules for those assets are also moved, copied, or deleted. If you rename a scheduled asset, that name will be reflected in the schedule. Keep the following impacts to schedules in mind when you move, copy, delete or rename assets:
Schedule changes when assets are moved
  • If the asset has its own schedule (is the only asset in a schedule), then that schedule will not change. That schedule will still be associated with the asset.
  • If the container from which you moved the asset has a schedule associated with it, the asset is removed from that schedule.
  • If the container into which you moved the asset has a schedule associated with it, the asset is added to that schedule, but with the default settings determined by the
    Options
    dialog box.
Schedule changes when assets are copied
  • If the asset has its own schedule (is the only asset in a schedule), that schedule will not change. That schedule will be associated with the original instance of the asset. So if you rename the original asset, the asset's new name will be reflected in the schedule. If you rename the new instance of the asset, the new asset is not part of the original asset's schedule.
  • If the container holding the original asset has a schedule associated with it, that schedule remains unchanged.
  • If the container into which the asset is copied has a schedule associated with it, the asset is added to that schedule, but with the default settings determined by the
    Options
    dialog box.
Schedule changes when assets are deleted
  • If you delete an asset, any schedule associated with that asset is also deleted. If the asset is included in a container that has a schedule associated with it, the schedules for other assets in the container are not affected.
Schedule changes when assets are renamed
  • If you rename an asset, the new name for the asset is reflected in the schedules for the asset.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal