web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Customer experience | Sales, Customer Insights,...
Suggested Answer

crmCreate is not defined / Automatic Record Creation and Update Rules

(2) ShareShare
ReportReport
Posted on by 11

Hi everyone,

 

When attempting to create a business rule for processing incoming emails using Automatic Record Creation and Update Rules in CRM, the following issue occurs:

  1. Step 1 – I create the rule and save it successfully.
  2. Step 2 – When trying to add a condition (New button), an error appears immediately upon opening the form.

Error Details:

  • Form Name: New Record Creation and Update Rule Item
  • Error Message:
    One of the scripts for this record has caused an error. For more details, download the log file.
    crmCreate is not defined
  • Function Name: Mscrm.Form_onload
  • Script File: ConvertRuleItem_main_system_library.js
  • Solution Name: System
  •  

Impact:

  • The condition form is incomplete.
  • It is impossible to create a condition due to the script error.
 
Instance is new, cloud, no tweaks or custom scripts, just installed.

 

I have the same question (0)
  • MW-15012107-0 Profile Picture
    2 on at
    Hi Oleg!
     
     Could you please download the log file and post the results?
  • Suggested answer
    Andrew Perkin Profile Picture
    34 on at
    Hi, 

    I know this is quite an old post, but I encountered this exact same issue today.

    If you try and create an RCR via any of the traditional routes like Power Platform Environment Settings, you get the javascript errors described when you create the condition.

    It seems Microsoft have created a new app, which is full of shiney new toys, called the CoPilot Service Admin Center. 

    In order to create an RCR which didnt fall over I had to use that app, and navigate to case Settings, Automatic recrod creation and update rules. From there it worked perfectly. Any other route throws many jscript errors.

    Maybe a redirect to that app from the traditional routes, would be better than the errors Microsoft....

    That might help someone wondering why things are broken.


  • Suggested answer
    AB-23050830-0 Profile Picture
    22 on at

    Problem

    You're receiving a JavaScript error (crmCreate is not defined) when attempting to add a condition to an Automatic Record Creation and Update (RCR) rule via the standard route. This blocks the form from loading properly community.dynamics.com.

    Solution & Recommended Steps

    1. Use the CoPilot Service Admin Center
      • I believe the legacy method (e.g., navigating through Power Platform Environment Settings or directly via CRM settings) triggers the script error.
      • Try going to the CoPilot Service Admin Center (a newer app/interface in Dynamics 365)
    CoPilot Service Admin Center
    Navigate to Automatic Record Creation and Update Rules
    • Within the CoPilot Service Admin Center, look under Case Settings.
    • You’ll find the “Automatic record creation and update rules” section here. Select ‘Manage >’.
    Automatic Record Creation and Update Rules
    1. Create or Edit the RCR Rule
      • From this app, create your RCR or edit an existing one.
      • You should now be able to add conditions without encountering the crmCreate script error.
    2. Save and Publish
      • Complete your rule setup.
      • Save and publish as usual—this route avoids the problematic JavaScript.
    3. Validate Operation
      • Test by sending an email or whatever trigger you have set up.
      • Ensure that the rule creates or updates the record as expected.

    Why This Should Work

    According to feedback from users encountering the same issue, the new CoPilot Service Admin Center employs updated scripts that avoid the errors seen in the older interface—in effect, Microsoft replaced the legacy method with a more reliable mechanism.

    Extra Tips

    • If you're unsure how to access the CoPilot Service Admin Center:
      • Check the App Launcher (waffle menu) in your Dynamics 365 environment.
      • Alternatively, navigate via the Power Platform admin center → select your environment → look for “CoPilot Service Admin Center”.
    • If your organization doesn't appear to have access, confirm that your Dynamics 365 plan is updated and your user role has sufficient Admin permissions.

    Summary Steps

    1. Open CoPilot Service Admin Center
    2. Go to Case Settings → Automatic Record Creation and Update Rules
    3. Create/Edit rule; add conditions smoothly
    4. Save & publish the rule
    5. Validate rule works correctly with test data

    To recap: avoid the script error by switching from the legacy settings path to the CoPilot Service Admin Center, that’s where RCR rules now work reliably.

     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
Pallavi Phade Profile Picture

Pallavi Phade 98

#2
Tom_Gioielli Profile Picture

Tom_Gioielli 60 Super User 2025 Season 2

#3
Gerardo Rentería García Profile Picture

Gerardo Rentería Ga... 43 Most Valuable Professional

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans