Hi Silvester,
I made a couple of financial interfaces that included GL transaction and I believe that oData will not survive with the amount of data flowing through the interface.
I still recommend you check BYOD scenario, the main advantage that you don't need a new entity, you can activate change tracking and export only new data every time to DB.
From the python side, you can use any ORM that supports Azure SQL to query data, like PeeWee pypi.org/.../
docs.microsoft.com/.../export-entities-to-your-own-database
If you still want to try new entity for oData,
Just duplicating entity is not enough, after you duplicated entity you need
1. Change the label property to make it unique
2. Change staging table property to make it unique or disable data management property
3. If you decided to keep data management enabled, open the context menu for entity and press "Regenerate staging table"
4. Set IsPublic property to Yes, fill public collection name (plural) and public entity name with unique value
5. Open new entity source code and replace all occurrences of GeneralJournalAccountEntryEntity with your new entity name
6. Create new security privilege and drop your new entity to data entity permission node and grant "read" access
After steps done, make a build and synchronize the project and entity will be available in oData, and data can be queried using Public collection name.
