If this is a bug in 2022, then I can think of upgrading my FME version to 2023. Please confirm.
Page 1 / 1
A possible workaround would be to read the date directly from the underlying database, e.g. using a DatabaseJoiner, SQLExecutor, etc. Example SQL:
SELECT myDateField
FROM mySchema.myFeatureClass
WHERE objectid = @Value(OBJECTID)
A possible workaround would be to read the date directly from the underlying database, e.g. using a DatabaseJoiner, SQLExecutor, etc. Example SQL:
SELECT myDateField
FROM mySchema.myFeatureClass
WHERE objectid = @Value(OBJECTID)
Is it a bug in SDE Reader?
As we do not have direct access to the database, therefore, I am unable to go with suggested options. We can access the data using SDE reader only.
Can you please suggest the other way around?
Is it a bug in SDE Reader?
As we do not have direct access to the database, therefore, I am unable to go with suggested options. We can access the data using SDE reader only.
Can you please suggest the other way around?
I've no idea where such a limit could occur.
Perhaps try using arcpy from FME?
Is it a bug in SDE Reader?
As we do not have direct access to the database, therefore, I am unable to go with suggested options. We can access the data using SDE reader only.
Can you please suggest the other way around?
I have exported the data to FGDB and tried to read it with 2023 version and it is reading it successfully. However, it's not reading correctly on 2022 version. I am looking into it by changing Python compatibility as well.
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.