Configure OdataLink to poll for changes: Difference between revisions

No edit summary
No edit summary
Line 18: Line 18:
It is easier to illustrate it's use with an example. If a transaction is moved from February to March, OdataLink can poll for changes in February but it is likely that MYOB or Xero would indicate no changes. This is because there are no modified transactions in February (since it is now in March). The sensitivity setting allows OdataLink to establish a wider date range.  
It is easier to illustrate it's use with an example. If a transaction is moved from February to March, OdataLink can poll for changes in February but it is likely that MYOB or Xero would indicate no changes. This is because there are no modified transactions in February (since it is now in March). The sensitivity setting allows OdataLink to establish a wider date range.  


When sensitivity is set to +/- 1 month, rather than constrict checking for changes only in February, it will send a call asking if anything changed in January to March. If the answer is yes, it will refresh February.  It will do the same for March by checking February to April.
When sensitivity is set to +/- 1 month, rather than constrict checking for changes only in February, it will send a call asking if anything changed in January to March. If the answer is yes, it will refresh February.  It will do the same for March by checking February to April and so on.


When sensitivity is set to +/- 2 month, it would use Ecember to April when checking for changes in February.
When sensitivity is set to +/- 2 month, it would use December to April when checking for changes in February.