-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide access to table definitions like DefinedNames #1454
Comments
Thanks for your issue. The library doesn't support listing table names and ranges currently. I will consider adding this feature. |
That would be great. I took a look and am not sure I can easily figure out the changes to add this feature, but it looks like the code already examines the tables refs in XML, so I guessing it is very close. |
The new functions |
…s GetTables and DeleteTable (qax-os#1573)
Description
It is possible to obtain the list of DefinedNames today, and that works well. In Excel (M365), Name Manager also lists defined Tables as named ranges.
In excelize, there are functions to add tables (AddTable()), but not to retrieve existing tables. Some of the private functions, such as countTables(), appear to be able to access the proper information about tables.
Ideally, existing tables should either be returned in DefinedNames() or in a new function such as Tables().
Tables are a very common structure in many Excel files, and I happen to use them extensively because of their power in providing structured references for use in formula functions such as XLOOKUP.
If this ability is already present, then I apologize for having missed it.
Describe the results you expected:
File.Tables() would return a list of tables defined in the workbook similar to File.DefinedNames(). The returned structure should include at least the name or the table and the reference to be useful, and ideally all the data that could be used in AddTable().
Output of
go version
:Excelize version or commit ID:
Environment details (OS, Microsoft Excel™ version, physical, etc.):
MacOS 12.6.2, Excel M365 current as of today
The text was updated successfully, but these errors were encountered: