M
Martyn Lawson
Hi,
Let me try to explain what i have in place:
I've got a secondary datasource linked to a SharePoint list with multiple
columns of different data types. In InfoPath I have a repeating table with
various columns.
I have a rule on one of the fields that uses the 'set a fields value' action
to populate another field with the data from the SharePoint list. I am doing
this using a filter on the action to find the correct row in SharePoint. This
is where the problem lies:
It appears that some of the fields in SharePoint cannot be used as a basis
for the filter - there is no error, just doesn't work. It is worth mentioning
that these rules have worked in the past and therefore I am pretty sure they
should now.
At first I thought it might be down to the datatype as none of the number
fields were working but the currency and text were. So i tried to create new
columns in sharepoint to use in the filter; however, none of these work -
regardless of the datatype.
It is fair to say that things have changed since the rules worked - too much
to revert back. However, i don't think that any of the changes would explain
why new columns in SharePoint (regardess of datatype) can be used
successfully.
I hope someone can at first understand the problem and secondly offer a
solution.
Kind Regards,
Martyn...
Let me try to explain what i have in place:
I've got a secondary datasource linked to a SharePoint list with multiple
columns of different data types. In InfoPath I have a repeating table with
various columns.
I have a rule on one of the fields that uses the 'set a fields value' action
to populate another field with the data from the SharePoint list. I am doing
this using a filter on the action to find the correct row in SharePoint. This
is where the problem lies:
It appears that some of the fields in SharePoint cannot be used as a basis
for the filter - there is no error, just doesn't work. It is worth mentioning
that these rules have worked in the past and therefore I am pretty sure they
should now.
At first I thought it might be down to the datatype as none of the number
fields were working but the currency and text were. So i tried to create new
columns in sharepoint to use in the filter; however, none of these work -
regardless of the datatype.
It is fair to say that things have changed since the rules worked - too much
to revert back. However, i don't think that any of the changes would explain
why new columns in SharePoint (regardess of datatype) can be used
successfully.
I hope someone can at first understand the problem and secondly offer a
solution.
Kind Regards,
Martyn...