Header file in TMDS and Datafinder

Question

I want to write my acquisition info to header file in TDMS.
My trial was seemed to be successful as you can see the attachment of TMDS viewer.png.
But, some extra stuffs can be seen in DataFinder toolkit.
(The searched folder contains only my custom TMDS files, no extra TDMS files.)
For example, I wrote "FileName" but seen as "fileName" or error in reading #channels in TMDS.png.
I am very wondering how can I control the keywords in Datafinder.
I reset the indexing but useless.
Doesn't it reliable way to find the TDMS data in Datafinder toolkit? or my mistake?
labmaster.
Attachments:
TDMS.png ‏108 KB
tmds_viewer.png ‏27 KB

Answer 1

In the TDM platform (this includes the DataFinder) there are some characters and some keywords which are handled in a special way (you find details below). Therefore the behavior you describe may appear.
You will find a list of searchable base attributes in the online help of the DataFinder Toolkit. Open the content tab of the LabVIEW help, open the node "Toolkits", then the node "LabVIEW DataFinder Toolkit" and go to the following page: "Properties".
Custom properties are always searchable with the following exceptions:
1. Some characters may be replaces with "_" (see information below)
2. Custom properties of the data type date/time have to be optimized to be searchable. Custom properties of other data types may be optimized but do not necessarily have to be.
Hope that helps,
Eva
I copied the following from another thread and added some DataFinder specific information:
The following characters are not supported for custom property names throughout the whole TDM platform :
., :, ,, ;, ', \, @, <, >, #, [, ], %, (, ), {, }, |, *, ?, =, !, ", ^, $, &, +, -, /, and a space
These characters will be replaced with "_" in the property name. (This is why you see #channels as _channels)
Also the following property names are reserved and may not be used for creating custom properties on file level:
author, channelgroups, children, datestring, datetime, description, environment, external_references, id, instance_attributes, mime_type, name, objecttype, parent, registercomments, registertxt1, registertxt2, registertxt3, timestring, title, version, version_date
Additionally the DataFinder has the following property names reserved on file level (This is why you see FileName as fileName.):
createTime, dataPluginName, fileName, folder, indexStatus, modifyTime
The following property names are reserved and may not be used on group level:
 channels, children, description, equipments, external_references, id, index, instance_attributes, measurement_begin, measurement_end, measurement_quantities, mime_type, name, objecttype, parent, registertxt1, registertxt2, registertxt3, root, sequences, submatrices, submatrices, test, units_under_test, version, version_date
The following poperty names are resevered and may not be used on channel level:
 average, channel, children, datatype, deletebehaviour, description, dimension, displaytype, empty, external_references, flagkey, group, groupindex, id, implicit_increment, implicit_start, instance_attributes, internal_params, internal_res1, internal_res2, interpolation, is_scaled_by, length, lengthmax, local_columns, maximum, measurement, mime_type, minimum, monotony, name, novaluekey, number, objecttype, parent, quantity, rank, registerint1, registerint2, registerint3, registerint4, registerint5, registerint6, registertxt1, registertxt2, registertxt3, registerval1, registerval2, registerval3, registerval4, registerval5, registerval6, representation, scales, sourcedatafilename, sourcedatafilepath, sourcegenparam1, sourcegenparam2, sourcehandle, sourceinstancekey, sourcename, sourceparentname, sourcerepresentation, sourcetype, sourcevalue, standard_deviation, status, type_size, unit, unit_string, valuetype, version, version_date, waveform,