Has anyone been successful at capturing a triggered send name to a data extension field by setting this to an ampscript variable. Imagine having 40+ different triggered sends that are tied to SOAP API calls that occur from a proprietary business application. This application was written years ago and is still in service. Requesting the app dev team to add a custom value to get passed to a custom field for each of the API calls to uniquely identified which record is associated with which triggered Send in the data extension is going to take significant time to get this type of project moved up as a priority on their project list and for them to recompile/build the application. I had thoughts that there must be an easier way to accomplish identification records by triggered send being added in a data extension. (Usually if we mapped only one data extension per triggered send that would make things easier but it would be consuming for 40+ triggers not to mention that if the data for all 40+ triggers were already being sent to one data extension for years...it would muddy the waters if queries had to be run on multiple data extension to get out the data instead of just one for all the triggers.)
We know that data extensions have the unique ability to self capture the date timestamp for a record when it is added by selecting the option to capture the current timestamp. Is it also possible that such functionality to be embedded into a data extension when that data extension is a Triggered Send Data Extension? If so, has anyone had any success with performing such as simple capture to a data extension without having to force feed a hard coded value as part of the API call to the Triggered Send definition.