3 added 594 characters in body
source | link

What have you tried? If you're just starting your search then the docs references below are a great start.

Both the TOM.NETTOM.NET and Core Service APIsCore Service APIs are available but it shouldn't be about what's easiest. It would be interesting to understand if there some technical or business reason you want to consider using the Event System?

If you have Alchemy installed, there's an app for that, https://www.alchemywebstore.com/plugins/Component-Synchronizer

If you haven't then the docs clearly show the core service approach - this is a good start: http://docs.sdl.com/LiveContent/content/en-US/SDL%20Web-v1/GUID-2B44D2F8-65E9-40DD-8408-DF1537BE50F5

The risk I see with an Event-driven approach would be

  • whether or not the process be followed to ensure content is checked/confirmed - since the synch was now done 'under-the-hood'
  • what error catching mechanisms will you have - will the team making schema updates 'v' the person running the synch task have the same knowledge/debug level
  • would 'just testing' a schema update now trigger off potential data loss resulting content updates

What have you tried?

Both the TOM.NET and Core Service APIs are available but it shouldn't be about what's easiest. It would be interesting to understand if there some technical or business reason you want to consider using the Event System?

If you have Alchemy installed, https://www.alchemywebstore.com/plugins/Component-Synchronizer

If you haven't then the docs clearly show the core service approach - this is a good start: http://docs.sdl.com/LiveContent/content/en-US/SDL%20Web-v1/GUID-2B44D2F8-65E9-40DD-8408-DF1537BE50F5

The risk I see with an Event-driven approach would be

  • whether or not the process be followed to ensure content is checked/confirmed - since the synch was now done 'under-the-hood'
  • what error catching mechanisms will you have - will the team making schema updates 'v' the person running the synch task have the same knowledge/debug level
  • would 'just testing' a schema update now trigger off potential data loss resulting content updates

What have you tried? If you're just starting your search then the docs references below are a great start.

Both the TOM.NET and Core Service APIs are available but it shouldn't be about what's easiest. It would be interesting to understand if there some technical or business reason you want to consider using the Event System?

If you have Alchemy installed, there's an app for that, https://www.alchemywebstore.com/plugins/Component-Synchronizer

The risk I see with an Event-driven approach would be

  • whether or not the process be followed to ensure content is checked/confirmed - since the synch was now done 'under-the-hood'
  • what error catching mechanisms will you have - will the team making schema updates 'v' the person running the synch task have the same knowledge/debug level
  • would 'just testing' a schema update now trigger off potential data loss resulting content updates
2 added 594 characters in body
source | link

What have you tried?

Both the TOM.NET and Core Service APIs are available but it shouldn't be about what's easiest. It would be interesting to understand if there some technical or business reason you want to consider using the Event System?

If you have Alchemy installed, https://www.alchemywebstore.com/plugins/Component-Synchronizer

If you haven't then the docs recommendclearly show the core service approach - this is a good start: http://docs.sdl.com/LiveContent/content/en-US/SDL%20Web-v1/GUID-2B44D2F8-65E9-40DD-8408-DF1537BE50F5

Is there some technical or business reason you want to consider using theThe risk I see with an Event System?-driven approach would be

  • whether or not the process be followed to ensure content is checked/confirmed - since the synch was now done 'under-the-hood'
  • what error catching mechanisms will you have - will the team making schema updates 'v' the person running the synch task have the same knowledge/debug level
  • would 'just testing' a schema update now trigger off potential data loss resulting content updates

What have you tried?

If you have Alchemy installed, https://www.alchemywebstore.com/plugins/Component-Synchronizer

If you haven't then the docs recommend the core service approach - this is a good start: http://docs.sdl.com/LiveContent/content/en-US/SDL%20Web-v1/GUID-2B44D2F8-65E9-40DD-8408-DF1537BE50F5

Is there some technical or business reason you want to consider using the Event System?

What have you tried?

Both the TOM.NET and Core Service APIs are available but it shouldn't be about what's easiest. It would be interesting to understand if there some technical or business reason you want to consider using the Event System?

If you have Alchemy installed, https://www.alchemywebstore.com/plugins/Component-Synchronizer

If you haven't then the docs clearly show the core service approach - this is a good start: http://docs.sdl.com/LiveContent/content/en-US/SDL%20Web-v1/GUID-2B44D2F8-65E9-40DD-8408-DF1537BE50F5

The risk I see with an Event-driven approach would be

  • whether or not the process be followed to ensure content is checked/confirmed - since the synch was now done 'under-the-hood'
  • what error catching mechanisms will you have - will the team making schema updates 'v' the person running the synch task have the same knowledge/debug level
  • would 'just testing' a schema update now trigger off potential data loss resulting content updates
1
source | link

What have you tried?

If you have Alchemy installed, https://www.alchemywebstore.com/plugins/Component-Synchronizer

If you haven't then the docs recommend the core service approach - this is a good start: http://docs.sdl.com/LiveContent/content/en-US/SDL%20Web-v1/GUID-2B44D2F8-65E9-40DD-8408-DF1537BE50F5

Is there some technical or business reason you want to consider using the Event System?