Can we determine or force a table name for features?

When a service is created from a CSV or xlsx file, it has the ability to be overwritten.


This feature service has an accompanying xlsx file which contains the data for the service. After templatization and deployment, this connection is lost and the overwrite capability goes away.

It appears this is occurring because the adminLayerInfo setting in the JSON doesn't contain a table name. See sample below.
```
{
"adminServiceInfo" : {
"adminLayerInfo" : {
"tableName" : "db_15533.user_15533.POLICE_PERSONNEL_POLICE_PERSONNEL",
"geometryField" : null,
"xssTrustedFields" : ""
}
}
}
```

Is there a way for us to templatize this by either forcing a unique table name or reading the table name of the deployed xlsx file?