0
Hi Bhusan,
Appreciate your response. See my response to all 3 links below:
- https://blogs.msdn.microsoft.com/chaks/2011/05/01/concept-leverage-sharepoint-workflows-with-external-lists-part-1/
This won't work because we are trying to replace the SQL Trigger alerts with Sharepoint 2013 workflows. Basically, we need to send out alerts if there is a change in data
- http://www.c-sharpcorner.com/blogs/sharepoint-2013-workflow-with-external-list
There is no real solution on this link (unless I missed it) but all this says is "The resolution provided by Microsoft is, to use the SharePoint designer workflow 2010 as the List Workflow action of the SharePoint 2013." Not sure what is actual solution
http://stackoverflow.com/questions/3408903/can-an-external-list-have-event-receivers
"A workaround seems to be to create the external content type in Visual Studio. That way you can add some code to the create method to do additional things." This might work.
I think more and more I am leaning towards creating a workflow feature/solution using Visual studio which sends out emails based upon any data change. I am in process of doing this and will post the entire solution once complete
Thanks again

0
Did you take a look at this
https://blogs.msdn.microsoft.com/chaks/2011/05/01/concept-leverage-sharepoint-workflows-with-external-lists-part-1/
http://www.c-sharpcorner.com/blogs/sharepoint-2013-workflow-with-external-list
http://stackoverflow.com/questions/3408903/can-an-external-list-have-event-receivers