• Font Size
  • S
  • M
  • L

Search via FAQ No.


  • No : 24478
  • Open Date : 2016/06/13 14:15
  • 更新日時 : 2020/09/16 14:22
  • Print

[DataSpider Servista] The date is deviated when registering the data using the Salesforce Adapter

When registering the data of the date from 1948 to 1951 using Salesforce Adapter, the date might be deviated by a single day. Explain the cause and its counter measures.
Category : 

Answer

*Contents linked from this page might be in Japanese.
 
■Specification Description
 
According to the Daylight saving time that was implemented from 1948 to 1951, when there is an update in the date in the daylight period of that relevant period, the date is deviated by a single day. The above mentioned is as per the specification when Salesforce API is used.
 
■ Counter Measures
 
Support with any of the following methods.
  • Apply [DSS30SP1_120220_03]
By using the following function that is added in the [DSS30SP1_120220_03], the data of the relevant period can also be registered as such.
 
According to the Daylight saving time that was implemented in Japan between 1948-1951, when the date type of fields (date) are updated with relevant daylight saving time period date (UTC date), though the date is slipped by a single day, we have added the function to update without considering (Assuming the passed date as JST date) the daylight.
 
Apply [DSS30SP1_120220_03], and use the above-mentioned function.
  • Logic based date adjustment
When upgrading and patch application are difficult, is it possible to create the process so as to adjust the date by combining the logic and detecting the data targeted for the daylight saving method? Can the process of the adjusting the date be made? The related logic information is described in the Reference Information.(*Contents linked from this page might be in Japanese.)
 
 
・Year acquisition logic
 
・Month acquisition logic
 
・Date acquisition logic
 
・Little logic
 
・Date calculation logic