If a SharePoint user has a Managed Metadata column that they need to set the value for in SimpleIndex, the value they must use is the unique ID for that metadata value, not the value itself.
To find the unique ID, go to a document library that uses the managed metadata column and view the documents in Datasheet view. The unique ID is the part before the semicolon in that column. In the example below, the ERM Classification of “Electric Deal Tickets” has an actual value of “1”.
You will need to have a document with each possible value in order to get all the values this way. If there are a great number of possible values, it is possible to use a script to download them or to pull them directly from the SharePoint database.
SharePoint 2013 & Office365
For SharePoint 2013 and Office365 you need to use the GUID identifier for the taxonomy term.To get the actual value for a managed metadata term, you can use the Unique Identifier that is displayed when you edit the terms in Term Store Management.
In order to get the full list of unique ID values, follow the steps on this here. Use this list to create an autofill table that will replace the text value with the unique ID and map that field to your column in the database.
Users may have access to other tables and views that aren’t in their schema. When connecting to the database these tables will show up in the list, but when you try to get the list of fields you get an “Invalid object reference” error.
To reference these tables, use [Schema].[Table] for the table name to explicitly reference the table.
You can also change the user’s default schema on the server to the one matching the table.
A third option is to create a view under the user’s default schema that selects the necessary records.
At the present time you cannot enter [Schema].[Table] in the wizard, so if you need to use this workaround configure the job in the wizard and modify the table name in the old job options screen.