Skip to content

Integration approach #3

Description

@nameduser0

Having looked at this briefly, I think it could be improved a lot.
I really like the embedded page idea (though the Frepple settings URL is not used), but replicating all the data into other doctypes isn't the way to go.

  • For Pages that don't have an ERPNext equivalent, create an embedded page. Even better if you can embed the whole frepple site in a single page! You can override the page template if necessary
  • For Data that does have an ERPNext equivalent, implement a bidirectional sync (import & export routine) for each type that maps the fields to the correct ones, no need to create any doctypes
  • For Data that does not have an ERPNext equivalent, implement a Virtual Doctype though frankly if you're embedding frepple in a page, why bother?

Yeah this isn't really production-ready. It translates the data multiple times:

Rather than using frappe.db.sql for everything, have a look at the DB API
Also you can schedule background sync jobs

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions