To avoid an unnecessary sync, we use a hash number that combines all field values in the Mapping so that if one of the fields in the mapping has been changed, the hash code is also changed, but If the...To avoid an unnecessary sync, we use a hash number that combines all field values in the Mapping so that if one of the fields in the mapping has been changed, the hash code is also changed, but If the field is not in the mapping then the hash is not changed and won't sync the item even if the modification time is after last sync on.
Normally the portfolio code is not visible to the user – it’s provided behind the scenes by the portfolio selection webpart that makes up the top part of the dashboard. The resulting report will show ...Normally the portfolio code is not visible to the user – it’s provided behind the scenes by the portfolio selection webpart that makes up the top part of the dashboard. The resulting report will show you a list of all of the dynamic queries for that report and, if the database server supports it, it will give a pass/fail indicator for each one (along with the more detailed error message).
