A blog series distilling QUANTITATIVE data concepts AND USE-CASES IN THE EINSTEIN ANALYTICS PLATFORM.
Interesting 'speed bump' I encountered with fiscal year dataflow transformations. When using SFDC digest, you can create fiscal year offsets if a firm has a different fiscal year than calendar yr. So 'Firm ABC' has a fiscal year from July 1, 2019 - June 30, 2020. You would use FY offset of 6 in the fields attribute BUT ONLY in an SFDC digest transformation. If you are external connectors , thus limiting you to digest xforms, you would have to create an extra compute expression xformation with the ff. attribute settings > type = date / toDate(myDate_sec_epoch) / MM-dd-yyyy format \ 6 as the FY offset. In either scenario, SF will create a myDate(FiscalYr) and myDate (FiscalMonth) which effectively 'BINS' your particular dateField into the correct fy classification. Given above scenario, myDate fiscals month and yr will be 1, 2019 if the myDate is July 2019 (ie start of Firm ABS's fiscal year) . IF no Xform was done, it would default to calendar yr which means July 2019 would have fiscal month and Year as 7, 2019 respectively.