Skip to main content

ERROR running force:org:create: You do not have access to the [ScratchOrgInfo] object

Error : - 

 ERROR running force:org:create:  You do not have access to the [ScratchOrgInfo] object

Solution :- 

To enable Dev Hub in an org:

  1. Log in as System Administrator to your Developer Edition, trial, or production org (for customers), or your business org (for ISVs).
  2. From Setup, enter Dev Hub in the Quick Find box and select Dev Hub.

    If you don't see Dev Hub in the Setup menu, make sure that your org is one of the supported editions.

  3. To enable Dev Hub, click Enable.
    After you enable Dev Hub, you can’t disable it.

Comments

Popular posts from this blog

is not a JMX compliant Standard MBean

I got the fallowing exception and issue solved. If your are using MBean , MBean Interface and Implementation should be in same package, Otherwise use MXBean. javax.management.NotCompliantMBeanException: MBean class comlanka.rest.controller.DataManagerController does not implement DynamicMBean, and neither follows the Standard MBean conventions (javax.management.NotCompliantMBeanException: Class comlanka.rest.controller.DataManagerController is not a JMX compliant Standard MBean) nor the MXBean conventions (javax.management.NotCompliantMBeanException: comlanka.rest.controller.DataManagerController: Class comlanka.rest.controller.DataManagerController is not a JMX compliant MXBean)         at com.sun.jmx.mbeanserver.Introspector.checkCompliance(Introspector.java:176)         at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:317)         at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522)        

git Update failed

  Issue -  when you work with a large team, the git repository may have many branch creation and deletion operations, sometimes we may getting git update failed, when we try to update the whole repository. Solution - Tyr >  git fetch -p -p, --prune After fetching, remove any remote-tracking references that no longer exist on the remote. Tags are not subject to pruning if they are fetched only because of the default tag auto-following or due to a --tags option. However, if tags are fetched due to an explicit refspec (either on the command line or in the remote configuration, for example if the remote was cloned with the --mirror option), then they are also subject to pruning.

Angular2 bind data only if form is submitted

How to bind data only if form is submitted in Angular2 This can be down with angular2 form handing with data-driven approach (User Angular  FormBuilder ). Template File <form [ngFormModel]='myForm' (ngSubmit)="onSubmit()"> <input type="text" [ngFormControl]="myForm.controls['userName']" /> <button type="submit">Submit</button> <button>Cancel</button> </form> <br>userName : {{originalUserName}} Angular Component Class export class AppComponent { myForm:ControlGroup; originalUserName:string; constructor(private _formBuilder:FormBuilder) { this.originalUserName = 'abc'; this.myForm = _formBuilder.group({ userName: [this.originalUserName] }); } onSubmit(form) { this.originalUserName = this.myForm.controls['userName'].value; } } GitHub Example Source