When using the SQL SP Service, the properties of the Smart Object is populated as soon as the method is created that
points to the custom stored proc. I noticed that the stored proc parameter names do not get mapped to the Smart Object
properties with an @ sign as prefix, which would mean the names do no tget mapped identically the same.
Example: My stored proc might have a parameter called @employeeID, this is mapped to the Smart Object as only employeeID.
If I execute the Smart Object within InfoPath using rules, I get an error message that there is no column "employeeID".
Does this mean one should change the Smart Object properties after mapping them from a stored proc so they reflect the true
names (incl @) as they are within the stored proc it self?