Ag-grid Enterprise License Key Free
Celena Angolo
The Enterprise version of AG Grid comes with more features and support via Zendesk. The features that are only available in AG Grid Enterprise are marked with the Enterprise icon (e) as demonstrated in the image to the right.
It is free to try out AG Grid Enterprise. Please take AG Grid Enterprise for a test run - you do not need to contact us in order to do so. All that we ask when trialing is that you don't use AG Grid Enterprise in a project intended for production.
When you do not have a license key installed then AG Grid Enterprise will display a invalid key watermark. If you would like to remove this watermark so it's not in the way, please send us an e-mail in...@ag-grid.com and get a trial license key.
AG Grid checks the license key without making any network calls. The license key is set once for the grid library - you do not need to set the license key for each instance of AG Grid that you create as it is set once statically into the AG Grid library. You must set the license key before you create an instance of AG Grid or AG Grid will complain upon creation that no license key has been set.
If you are distributing your product and including AG Grid Enterprise, we realise that your license key will be visible to others. We appreciate that this is happening and just ask that you don't advertise it. Given our product is JavaScript, there is little we can do to prevent this.
If you have purchased the Enterprise Bundle (licenses for both AG Grid Enterprise and AG Charts Enterprise) then you will have ONE license key. This license key will work for both AG Grid Enterprise and AG Charts Enterprise.
i have tested some components with ag-Grid community edition but it has limited supportability, such as to add set filters using SetFilterModule, so the filter boxes would appear under the column header name, cannot be done with community version, therefore i have uninstalled the community version and installed the enterprise version using npm command
But when i tried to import AgGridModule from the import statement in the app.module.ts it did not show AgGridModule on the drop down. As shown on the image below, it had only three options LicenseManager, SetFilter, VirtualList. so, It had given me the impression that it required a license. But according to agGrid website i can use the full enterprise version of the grid without a license and the only barriers it will add are water marks and the console error message.
Therefore can anyone provide me on the steps on how to install the agGrid enterprise version and run it without a license key ( with watermark and console error messages )?
I did finally find reference to @ag-grid-community/angular in their docs, Modules Overview page, which also outlines all of the modules to install for specific features, both community and enterprise, instead of installing @ag-grid-enterprise/all-modules: -grid.com/angular-data-grid/modules/
In this post, we are going to demonstrate how you can minimise your application bundle size when working with AG Grid. This can be important if you want to improve your page load times, especially over slower networks. We will also detail the simplest way to include AG Grid if bundle size is not a particular concern to your application, i.e your application is only served over a high-speed internal network.
Before we start it's important to cover our AG Grid terminology to avoid confusion when reading our documentation of this post. For including AG Grid in your application we refer to packages and modules as two alternative methods. These terms are overloaded and have nothing to do with how the code is published or consumed by you. Don't confuse these terms with the different Javascript module formats such as CJS, ESM, UMD...
By packages, we are referring to the npm packages ag-grid-community and ag-grid-enterprise which contain all the community/enterprise features respectively. Think of them as all the AG Grid features packed up into a single package, hence the term package. They have everything packed in and are ready to go. Packages Overview
If you want to minimise your bundle size then you should use AG Grid Modules to only include code for the features that your application requires. For example, your application may not need to export files to Excel, so let's not include the code to support this.
If it is not clear from the name alone then you can also see which modules are required for a particular code example by selecting the 'Module' option. Then view the source code and you will see the required modules being imported.
Make sure you have not accidentally included any other AG Grid package, especially not ag-grid-community or ag-grid-enterprise when working with modules as they will dramatically bloat your bundle size!
You may have noticed that we have not explicitly included the module @ag-grid-community/core in our package.json but it will still be installed as a dependency of our modules. You are free to include it as you may find it is required for some linting tools.
Now that we have installed our modules the next step is to register them in our application with AG Grid. There are two ways to achieve this. You can either register them globally via the ModuleRegistry or pass them to a grid instance which will register them globally on your behalf. See Registering AG Grid Modules for the full instructions/framework-specific details.
A common fear that people have when working with modules is that they will not know exactly which modules they should include. In the majority of cases, AG Grid will warn you if you have enabled a feature but have not provided the required module. For example, if you add the rowGroup flag to your column definition but have not included the RowGroupingModule then you will see the following console warning.
The main exceptions to this rule are the SetFilterModule and MenuModule. If the SetFilterModule is present then the default filter becomes a set filter instead of the simple text filter. Likewise, if the MenuModule is present then right-clicking the grid will bring up the grid's context menu instead of the browser menu.
If minimising your application bundle size is not a priority then you should prefer AG Grid packages. Using the packages ag-grid-community and ag-grid-enterprise is comparatively simple. Your package.json file will only ever contain these dependencies, (plus your framework package, ag-grid-angular, ag-grid-react, ag-grid-vue3);
That's it! There is no need to register any modules as the packages do this for you. As you can see this makes for a much simpler developer experience and means that any new features will immediately be available to your application.
For example, the recently added Sparklines feature will be ready to use with no build changes unlike with modules where you will need to add the module to your package.json file and remember to register it too.
To give some concrete figures to our example we set up a grid with the above features in two React applications, one using Packages and one using Modules. As you can see only including the features that we require led to a 43% reduction in the final application bundle size.
When searching npm you may come across the packages @ag-grid-community/all-modules and @ag-grid-enterprise/all-modules and wonder what these are. These are provided for backwards compatibility but are no longer supported. They were wrappers that included all other modules but did not register them for you like their corresponding packages. They are not tree shakeable so even though you may only import one or two features you will still end up with all the code being included.
If you are using either of these modules we would recommend that you either switch to use packages and your bundle size should not be impacted. Alternatively, audit which features you require and just import and register those modules which will result in a reduced bundle size for your application.
In v30 the default export for our code has been updated to ES6 ES Modules. In our testing, by upgrading to v30 with no code changes, you can expect to see a bundle size reduction of anywhere between 5-10%. This applies to both AG Grid Modules and Packages.
We have seen how you can reduce your application bundle size by only including the AG Grid features that your application requires. This does require more developer effort so do consider if it is 'worth it' for you otherwise just enjoy the simplicity and full feature set of our packages.
For the first one you even explained that client-side can handly 100k rows and infinity row option is also available. Thanks for the info!
The the export-to-Excel thing, I thing we can figure out something else (e.g. sql-to-Excel or something like that).
Hi, export to csv with or without filtering is also available out of the box in the community version of Dash AG grid. Excel is available in Enterprise (obviously you can implement it also quite easily with external libraries)
Have used Datatable for some years, but switched now completely to Dash AG Grid.
Extreme awesome product and many thanks to the Dash team to make it available for us!!!
To get an overview what all is possible in Dash AG grid I highly recommend to go through all the examples provided in @AnnMarieW fantastic repo GitHub - plotly/dash-ag-grid . Well worth spent hours!!!
AG Grid has enterprise features available that let you add advanced functionality to your grids. If you have an AG Grid Enterprise license, you can use it with Dash AG Grid. Enterprise-only features include:
This example uses a licenseKey and has enableEnterpriseModules enabled. One of the AG Grid Enterprise features shown here is the Column Menu, which when you select it in a column header gives you access to options to pin, autosize, and reset columns. You can also hide/display columns from the Column Menu:
4a15465005