Hi Team,
Kindly assist!
Case-14694619 | WORKSPACE API
I have used the Eikon API for quite a few years now. I rewrote the code to use the LSEG-data API. - The Eikon API has worked very well with no problems - The LSEG-data API has problems. So, I am not asking for coding help,
I am pointing out a problem with the LSEG-data API. The following code works when configured for the Eikon API worked fine.
Configured for LSEG-data causes problems. It is not the code, it is the LSEG-data API that is not behaving correctly.
df = ld.get_data( universe=['BP.L',"GM.N",'F.N','STLAM.MI','JPM.N','META.OQ','HD.N'], fields = ['TR.RICCode', 'TR.OrganizationID', 'TR.CommonName', 'TR.DilutedEPSExclExtra', 'TR.DilutedEPSExclExtra.fperiod', 'TR.DilutedEPSExclExtra.periodenddate', 'TR.EPSNormalizeddil', 'TR.EPSNormalizeddil.fperiod', ' TR.EPSNormalizeddil.periodenddate', 'TR.EPSActValue(ActType=Reported)', 'TR.EPSActValue.fperiod', 'TR.EPSActValue.periodenddate', 'TR.EPSNormalizeddil.TTM', 'TR.EPSNormalizeddil.TTM.fperiod', 'TR.EPSNormalizeddil.TTM.periodenddate', 'TR.PriceClose', 'TR.PriceClose.date'], parameters = {'Frq':'M', 'SDate':0, 'EDate':-11, 'RH':'IN', 'Null':'Blank'} )
df.to_csv(rf'C:\Data_aaPython\Paul_Test_Earnings1.txt', header=True, sep='\t', index=False) print (df)
The ‘TR.EPSNormalizeddil.periodenddate’ column of data is shifted to the last column rather than being positioned after 'TR.EPSNormalizeddil.fperiod’. as a result, all the columns after 'TR.EPSNormalizeddil.fperiod’ are in the wrong position creating a problem for the code that is looking for specific data. This does not happen with the Eikon API.
Client is not asking for code or assistance on this, he clearly mentioned that the same code in LSEG Api in workspace, gives different output - he is pointing the problem of Api behavior itself.
product specialists suggested to check with your team to check further for if this is indeed a bug or just a format change.
Please check and provide your comments on this.
