[12.0] [ADD] Added connector_alndata module.

[nikitavaghela]

• created connector_alndata module
• Added fields
• Added tree, form views and action and menu
• Added scheduler and check credential using ALN API.

#48

[oca-clabot]

Hey @nikitavaghela, thank you for your Pull Request.

It looks like some users haven't signed our Contributor License Agreement, yet.
You can read and sign our full Contributor License Agreement here: http://odoo-community.org/page/cla
Here is a list of the users:

• @nikitavaghela (login unknown in OCA database)

Appreciation of efforts,
OCA CLAbot

[max3903]

@nikitavaghela Few comments:

• One file per class. Don't mix classes in the same file.
• No need for a new class apartment. Apartments should be mapped to fsm.location as mentioned in the mapping table.

[nikitavaghela]

Hello @max3903, All comments are resolved. Please review this.

[nikitavaghela]

@max3903 Fix the duplicate constraint issue because of archived data when fetching apartment data. Travis is failed because of NewConstructions data which not available on alndata.com

[nikitavaghela]

Hello @mgosai, I updated code as your approach please review it.

[nikitavaghela]

Hello @mgosai and @max3903,

As per the @mgosai approach, I added the customer_id field with required=True in the connector_alandata module. But there is raised an issue of NOT NULL constrain like this

so to fix this issue I added pre-hook and it's working fine.

Now issue that
if connector_alndata module installed first so it will added customer_id with NOT NULL constraint
and then if we are installing fieldservice_account_analytic module then raised error like this

or if we installed first fieldservice_account_analytic module then installing connector_alndata module then same error occurred

[nikitavaghela]

Hello @mgosai , @max3903 ,

Fixed the customer_id NOT NULL constrain issue for connector_alndata module.

Can you please review this?

[github-actions]

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.