Bresleveloper Digital - the best at SharePoint, PowerApps and Office365

 You need to use "empty" expression on the Lookup Value and Condition equals to expression "true" (of false or not equal ect.)

 If you get this kind of error Node Sass does not yet support your current environment: Windows 64-bit with Unsupported runtime (83) or any other kind of gulp build errors, and if its after you upgraded to Node 14.X, and upgraded your YO generator, then its because all the dependencies changed, and you need to migrage. so here is a simple solution: 1. Create a side clean SPFx project (Webpart or Extension (Extension is only with 2019+)) 2. Save somewhere (just in case) the following files  package.json, tsconfig.json, package-lock.json 3. Copy from your new project to your old project only 2 files   package.json, tsconfig.json * change the name and version of your project in the package.json file 4. Run gulp clean 5. Run npm install 6. Run gulp build ect.

 /sites/Portal/Lists/List10/DispForm.aspx?ID=4 /sites/Portal/Lists/List10/EditForm.aspx?ID=4

Are you working with SharePoint 2019? Maybe making some SPFx Extensions?  popstate not working?  click not working?  MutationObserver not working?  well, take a look at this As you can see, Microsoft are intercepting every click in the page, while stopping any bubbling. Therefor, any window/document/body onclick event will not work, in case you are trying to globally catch it. Same for popstate or MutationObserver. *Note - on SPO it seems that popstate event works. Solution - make an interval to keep watching href change: let   xPrevLocation  =  location . href let   xOnLocationChangeFunctions  = [] setInterval (() => {      if  ( location . href  !=  xPrevLocation ){          console . log ( "interval location change" ,  xPrevLocation ,  location . href )          xPrevLocation  =  location . href          for  ( let   i = 0 ;  i < xOnLocationChangeFunctions . length ;  i ++){              xOnLocationChangeFunctions [ i ]();         }     } },  350 ) Usage: window [ &#

  Error loading debug script. Ensure the server is running and the "debugManifestsFile" parameter URL is correct. Error: Script error for " https://localhost:4321/temp/manifests.js " SOLUTION browse to  https://localhost:4321/temp/manifests.js  and allow to proceed to unsafe, and refresh the original page

 White you can use the pnp-generator , I really wanted to created this kind of solution all by myself, since I also wanted to implement it with SP-2019, with SFPx 1.4.x Part 1: Setup I started with a clean machine, installed LTS node 14.17.0 , and installed latest gulp, yo, sp-generator for yo, and angular-cli command: npm install gulp yo @microsoft/generator-sharepoint --global results: + gulp@4.0.2 + yo@4.2.0 + @microsoft/generator-sharepoint@1.12.1 command: npm install -g @angular/cli results: + @angular/cli@12.0.2 *NOTE - To the time of writing, I had an error generating browser application bundles so I downgraded to angular 10.x, and re-create the project npm uninstall -g @angular/cli npm cache clean --force npm install -g @angular/cli@10.2.0 And so our journey begins! Create new Ng project ng new ng-for-spfx-ex Create new SPFx WebPart Project - just  yo Part 2: Test NG with SPFx Within the  angular.json   file lets change the output path, I've made 1 folder, within I created