Virtual Doctype Error

RWEMA_Aimable · June 10, 2021, 12:43pm

I am trying the new Virtual Doctype using the example on this page: Virtual DocTypes

When I list or refresh the doctype, I get a TableMissingError as if the framework is expecting a database table to exist

12:25:14 web.1            | Traceback (most recent call last):
12:25:14 web.1            |   File "/workspace/development/frappe-13/apps/frappe/frappe/app.py", line 68, in application
12:25:14 web.1            |     response = frappe.api.handle()
12:25:14 web.1            |   File "/workspace/development/frappe-13/apps/frappe/frappe/api.py", line 54, in handle
12:25:14 web.1            |     return frappe.handler.handle()
12:25:14 web.1            |   File "/workspace/development/frappe-13/apps/frappe/frappe/handler.py", line 31, in handle
12:25:14 web.1            |     data = execute_cmd(cmd)
12:25:14 web.1            |   File "/workspace/development/frappe-13/apps/frappe/frappe/handler.py", line 67, in execute_cmd
12:25:14 web.1            |     return frappe.call(method, **frappe.form_dict)
12:25:14 web.1            |   File "/workspace/development/frappe-13/apps/frappe/frappe/__init__.py", line 1174, in call
12:25:14 web.1            |     return fn(*args, **newargs)
12:25:14 web.1            |   File "/workspace/development/frappe-13/apps/frappe/frappe/__init__.py", line 609, in wrapper_fn
12:25:14 web.1            |     retval = fn(*args, **get_newargs(fn, kwargs))
12:25:14 web.1            |   File "/workspace/development/frappe-13/apps/frappe/frappe/desk/reportview.py", line 44, in get_count
12:25:14 web.1            |     return execute(**args)[0].get('total_count')
12:25:14 web.1            |   File "/workspace/development/frappe-13/apps/frappe/frappe/desk/reportview.py", line 47, in execute
12:25:14 web.1            |     return DatabaseQuery(doctype).execute(*args, **kwargs)
12:25:14 web.1            |   File "/workspace/development/frappe-13/apps/frappe/frappe/model/db_query.py", line 101, in execute
12:25:14 web.1            |     self.columns = self.get_table_columns()
12:25:14 web.1            |   File "/workspace/development/frappe-13/apps/frappe/frappe/model/db_query.py", line 338, in get_table_columns
12:25:14 web.1            |     return get_table_columns(self.doctype)
12:25:14 web.1            |   File "/workspace/development/frappe-13/apps/frappe/frappe/model/meta.py", line 49, in get_table_columns
12:25:14 web.1            |     return frappe.db.get_table_columns(doctype)
12:25:14 web.1            |   File "/workspace/development/frappe-13/apps/frappe/frappe/database/database.py", line 896, in get_table_columns
12:25:14 web.1            |     raise self.TableMissingError('DocType', doctype)
12:25:14 web.1            | pymysql.err.ProgrammingError: ('DocType', 'Customer')

peterg · June 10, 2021, 7:06pm

Virtual Doctypes aren’t really working yet, or at least it’s not clear to me how to get them to work. There’s some discussion and fixes in the pipeline, but not clear when it will all be merged:

github.com/frappe/frappe

feat: Virtual DocType

frappe:develop ← zerodha:virtual_doctype

opened 11:33AM - 23 Dec 20 UTC

Thunderbottom

+175 -19

## Summary Virtual DocType is a feature-extension for DocType which allows de…velopers to create DocTypes with custom data sources and DocType controller. The purpose is to define custom DocTypes in the system without creating a table in the database, while utilizing the frontend, resource APIs, and roles and permissions from the framework. These Virtual DocTypes function exactly like normal DocTypes in the frontend and are indistinguishable for the end-user, but gives more control to the developer over the DocType's data source. With this, the data source for a Virtual DocType can be anything: an external API, a secondary database, JSON or CSV files, etc. This enables the developers to plug-in database backends other than MariaDB and Postgres, and makes the Frappe Framework even more powerful! ## Usage ### Creating a Virtual DocType To create a Virtual DocType, just select the **Virtual DocType** checkbox while creating the DocType: ![image](https://user-images.githubusercontent.com/11243138/102988812-8bc07e00-453a-11eb-9522-b0807fdf5675.png) ### Creating a Custom Controller As an example, the following controller code uses a JSON file as the DocType datasource: ```python class test_virtual(Document): def db_insert(self): d = self.get_valid_dict(convert_dates_to_str=True) with open("data_file.json", "w+") as read_file: json.dump(d, read_file) def load_from_db(self): with open("data_file.json", "r") as read_file: d = json.load(read_file) super(Document, self).__init__(d) def db_update(self): d = self.get_valid_dict(convert_dates_to_str=True) with open("data_file.json", "w+") as read_file: json.dump(d, read_file) def get_list(self, args): with open("data_file.json", "r") as read_file: return [json.load(read_file)] ``` To integrate other datasources with the Virtual DocType, you will need to add controller methods defining the database access. ### Outcome * The frontend for Virtual DocTypes remain unchanged: ![image](https://user-images.githubusercontent.com/11243138/102990099-cf1bec00-453c-11eb-8551-8e9a87f07db0.png) * All the `/api/resource` methods defined by the framework are compatible with Virtual DocTypes. --- Documentation Link: https://github.com/frappe/frappe_docs/pull/71

CA_B.C_Chechani · June 10, 2021, 11:48pm

Many Important newly released Features does not work. Like Custom DocType Layout does not work also - released a long time back . Setting Autoname instead of naming series does not work .Custom Doctype and Virtual Docs are the backbones for designing the system in every different way.

It’s difficult to understand what policy the Frappe team have to include such not working features ( Not working at all - not bugs ) . And they can be fixed easily too

mymi14s · September 20, 2021, 8:15am

@RWEMA_Aimable
You can check out this YouTube tutorial on virtual doctype