Miguel Carreon The current code of the class component can be found here You need to change the class component to a function component. The current component is stateless, so you need to replace all class methods with functions and it should work. Alternatively, you can use my npm package @spfxappdev/fluentui-react-controls which contains also this control A Live demo (PnP community call) is here: https://www.youtube.com/watch?v=nxG7n4e2Xlc

Jonathan Adcox Hmmm, where exactly is the error? I've never had this before. I use npm run publish and this command does a gulp clean and then a gulp build , gulp bundle --ship , gulp bump-version and then gulp package-solution --ship one after the other. Normally only the patch version is updated, unless you specify something else. By the way: If you use the command npm run publish and there was a warning/error in the console output, then the commands are not executed, with the output exit with code 1 (or something like that). This is due to the && command combination. But you can prevent this by disabling the warnings. PS: As mentioned in the other comments, I can recommend using my CLI, which does exactly the same settings as described in this article, and does so with a command line and also adds the "disable warnings" command. And some more. Here is the link to the CLI article (with Video): https://spfx-app.dev/my-cli-for-spfx-development

Thank you Jonathan Adcox Just for me out of interest. Does your comment only refer to the Gulp commands (from the article) or also to the CLI (which I mentioned in the comments)? BTW: If you're interested, I also have an article on how you can integrate the same logic into an Azure DevOps pipeline to increment the version, create the package and create another Git tag with the same version number

Hi Miguel Carreon What do you want to do? Do you want to use this class component in a functional component (hooks) in SPFx? Or would you like to know how you can "rebuild" the component with hooks?

Hi, I'm not sure if I understand you correctly or what you are planning to do! You want two different "environments" on the same tenant with possibly different versions of the web part(s)? If yes, create a site collection app catalog and deploy it in the site collection only.

Thank you Denny Regehr I will think about it. Maybe I can find a solution for it.

Hi Denny Regehr thank you for your comment and the idea. Just to be sure I understand it correctly. Do you mean a note field where the TEXT of the certificate is stored? Or do you mean a certificate field as an attachment? Regarding the expiration date and notification: A TimerJob or something similar is needed for this request. The next problem is: all data is encrypted and can be decrypted ONLY with the master password. This means: the expiration date cannot be read if it is not decrypted and this is only possible with the master password. And I/the timer job do not know the master password. That means you would have to implement the same encryption and decryption logic in the timerjob (The timerjob would have to know the page URL, webpart instance ID and the masterpassword (not hashed)). In addition, there are fees for the TimerJob. I think it would be easier in this case to just take a list, (possibly only for a certain group of people) and build a flow that determines the date from the items and notifies you. The certificate itself doesn't even have to be stored in the list, it could still be in the WebPart :-)

Hi Adagal13 , a new version was released

Hi Adagal13 thanks for the comment. I am currently working on a new release. The next release will be developed with SPFx 1.16 and will include as many username/password combinations as you want. And this solution will be available on PnP samples too. Thank you for using my web part. Greetings from Germany Seryoga

Mathias Nitzsche Yes, I know/understand. I just wanted to let you know.