Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

Random questions

Michael D

January 22, 2019 16:15

What is the maximum/limit to how many custom fields you can create in PDQ Inventory? I am still using version 13.3 because of Windows XP.

Before I am doing mass-import of CSV files via commandline, I am exporting the custom fields from the database using the the script from this guide: https://www.pdq.com/blog/export-custom-fields-pdq-inventory-using-powershell-sqlite/ It has worked fine, but I suddenly noticed that most of the non-english characters are not displayed correctly. I my case it was the danish "æ å ø". Is it possible to modify the script to correct this or is this a known limitation?

When do you plan to phase out support for Windows 7? Microsoft extended support stops Jan 2020.

Comments

1 comment

Colby Bouma
June 30, 2021 03:53
What is the maximum/limit to how many custom fields you can create in PDQ Inventory?

I do not believe there is a limit. At some point you'll probably run into performance problems, but I don't know if that's at 100 or 10,000 Custom Fields.

I am exporting the custom fields from the database...most of the non-english characters are not displayed correctly.

I just tested with Get-PdqCustomField from my PowerShell module PdqStuff, and it seems to work correctly.
```
Install-Module -Name 'PdqStuff'
Import-Module -Name 'PdqStuff'
Get-PdqCustomField
```
When do you plan to phase out support for Windows 7?

PDQ tends to keep working with OSs long after support ends. The only reason PDQ stopped working with XP is because of the update to .NET 4.5.2 in 14.1.0.0 (the current requirement is 4.6.1).
0