TapeTrack Documentation

Because there is more to tape management than you ever realized

User Tools

Site Tools


engine:sync:addmovedateadjustment

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
engine:sync:addmovedateadjustment [2018/08/13 22:46] dcummingengine:sync:addmovedateadjustment [2025/01/21 22:07] (current) – external edit 127.0.0.1
Line 1: Line 1:
-===== Name ===== +====== AddMoveDateAdjustment ======
-addmovedateadjustment +
- +
-==== AddMoveDateAdjustment ====+
 Add a specific number of days, months, years to the Next Move Date if a field value matches a filter value. Add a specific number of days, months, years to the Next Move Date if a field value matches a filter value.
  
-==== Phase ====+===== Phase =====
 This instruction is used by the TapeTrack Synchronization Engine. This instruction is used by the TapeTrack Synchronization Engine.
  
-==== Syntax ==== +===== Syntax ====
-**AddMoveDateAdjustment**//(field, filter, years, months, days);//+ 
 +''AddMoveDateAdjustment(field, filter, years, months, days);'' 
 + 
 +^ Variable ^ Type ^ Description ^ Min Length ^ Max Length ^ Min Value ^ Max Value ^ 
 +|field  | String | The field to compare against. | 1|40| 
 +|filter | String | A filter value to compare the field value against. |1|256| 
 +|years | Integer | The number of years to add to the Next Move Date. |1|10|-214748364 | 2147483647| 
 +|months | Integer | The number of months to add to the Next Move Date. |1|10|-214748364 | 2147483647| 
 +|days | Integer | The number of days to add to the Next Move Date.|1|10|-214748364 | 2147483647| 
 + 
 +==== Example ====
  
-//string field;//+Add 7 years to the Next Move Date if the Description contains YEARLY
  
-//string filter;//+<code> 
 +
 +# Extract the MOVEDATE from offset 4, length 10 of the report body. 
 +Extract(MOVEDATE, 4, 10, 0);
  
-//integer years;//+# Set the MOVEDATE format. 
 +SetMoveDateFormat("%%d/%%m/%%Y");
  
-//integer months;//+# Extract the DESCRIPTION from offset 5, length 100 of the report body. 
 +Extract(DESCRIPTION, 5, 100, 0);
  
-//integer days;//+# Adjust the extracted MOVEDATE by 7 years if the DESCRIPTION matches the pattern *YEARLY*. 
 +AddMoveDateAdjustment(DESCRIPTION, "*YEARLY*"7, 0, 0); 
 +</code>
  
-|field  |The field to compare against. | +===== See Also =====
-|filter |A filter value to compare the field value against. | +
-|years |The number of years to add to the Next Move Date. | +
-|months |The number of months to add to the Next Move Date. | +
-|days |The number of days to add to the Next Move Date.|+
  
-==== Examples ==== +[[engine:import|Import Engine Functions]] \\ 
-**AddMoveDateAdjustmentAdd 7 years to the Next Move Date if the Description contains YEARLY** +[[cli:sync_fields|Sync Engine Fields]] \\ 
-|Extract(MOVEDATE, 4, 10, 0); |Extract the MOVEDATE from offset 4, length 10 of the report body.+[[cli:tmss10sync|TMSS10Sync]]
-|SetMoveDateFormat("%%d/%%m/%%Y");|Set the MOVEDATE format.| +
-|Extract(DESCRIPTION, 5, 100, 0);|Extract the DESCRIPTION from offset 5, length 100 of the report body.| +
-|AddMoveDateAdjustment(DESCRIPTION, "*YEARLY*"; 7, 0, 0);|Adjust the extracted MOVEDATE by 7 years if the DESCRIPTION matches the pattern *YEARLY*.|  +
  
 +{{tag> import_engine}}
engine/sync/addmovedateadjustment.1534200370.txt.gz · Last modified: 2025/01/21 22:07 (external edit)