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

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / creating new solution ...
Power Apps
Suggested Answer

creating new solution and publisher best practices

(0) ShareShare
ReportReport
Posted on by 36
Hi,

If let's say i want to create a new product called "SellOps"

can someone please answer my 4 questions?
 
1. Shall i create a solution with the same name?


2. Also should  the publisher be the same name of the product or owner name?



 
3. should the prefix be the first initials of the solution name or publisher name? "so" for sellOps and "mn" if i name the publisher with my name?

4. Also here why the name for the publisher wasn't filled automatically without spaces just like the name of the solution? should i fill it with spaces or not?
 

 
I have the same question (0)
  • Suggested answer
    MS.Ragavendar Profile Picture
    6,334 Super User 2026 Season 1 on at
     
    Follow the naming standard and best practice document
     
     
     
     
     
     
    Please click Accept as solution if my post helped you solve your issue and help others who will face the similar issue in future.
    ❤️ Please consider giving it a Like, If the approach was useful in other ways.
    🏷️ Please tag me @MS.Ragavendar if you still have any queries related to the solution or issue persists.
  • DELDYN Profile Picture
    36 on at
    Hi,
     
    Thanks for the reply but it doesn't answer my 4 questions.
     
    My question is about solution and publisher. Not about canvas app
  • Suggested answer
    Vejai SH Profile Picture
    560 on at
    Hi @DELDYN,
     
    Normally, Publisher refer to department or a company.
     
    1. Shall i create a solution with the same name?  Yes, it can be the same. if you want to keep it simple 
    2. Also should  the publisher be the same name of the product or owner name? 
    Publisher should represent the organization or vendor, not the product.
    If SellOps is the product and your company is MindNest, the publisher should be:
    • Display Name: MindNest

    • Schema Name: mindnest

     

    3. should the prefix be the first initials of the solution name or publisher name? "so" for sellOps and "mn" if i name the publisher with my name? Prefix is based on publisher

    • If your publisher is MindNest, then use prefix mn.
    • If you used SellOps as publisher (not recommended), you could use so.
    Example
    Let’s say you create a custom table “Project”.
    • With publisher MindNest (prefix mn), it becomes mn_project.
    • With publisher SellOps (prefix so), it becomes so_project.
    4. Also here why the name for the publisher wasn't filled automatically without spaces just like the name of the solution? should i fill it with spaces or not? That’s expected — and by design.
    • Display Name: With spaces → “MindNest Solutions”
    • Name (Schema Name): Without spaces → “mindnest”
    • Prefix: “mn”
     
     
    Thanks, 
    Vejai SH  
     
    Please mark as answer if my suggestion helps you
     
  • Suggested answer
    MS.Ragavendar Profile Picture
    6,334 Super User 2026 Season 1 on at
     
    1. Shall i create a solution with the same name?
     
    Yes, that's usually best practice.
     
    2. Also should  the publisher be the same name of the product or owner name?
     
    Company Wide - Company / brand name
     
    Multiple Product from one Org - Organization name as publisher.
     
    because this helps us who offered which solution in the time being.
     
    3. should the prefix be the first initials of the solution name or publisher name? "so" for sellOps and "mn" if i name the publisher with my name?
    Prefix name comes from published it is not coming from solution name.

    4. Also here why the name for the publisher wasn't filled automatically without spaces just like the name of the solution? should i fill it with spaces or not?
    The solution name automatically become system name (no white spaces) but published name is a input field which you are filling the publisher details.
     
    Please click Accept as solution if my post helped you solve your issue and help others who will face the similar issue in future.
    ❤️ Please consider giving it a Like, If the approach was useful in other ways.
    🏷️ Please tag me @MS.Ragavendar if you still have any queries related to the solution or issue persists.
  • DELDYN Profile Picture
    36 on at
    Hi Vejai,

    So if i go with publisher name as company name like this
    Display Name: With spaces → “MindNest Solutions”
    Name (Schema Name): Without spaces → “mindnestsolutions”  (all small letter)

    and for the solution
    Display Name: With spaces → “Sell Ops”
    Name (Schema Name): Without spaces → “SellOps”  (it gets filled automatically without spaces, but it didn't make it all small letter, the system made it like this SellOps (just removed spaces))

    so does that mean that publisher  scheme name should be all small letter, but solution scheme name can still be capatialized, as it got auto filled with capital letter?
  • Vejai SH Profile Picture
    560 on at
    Hi,
     
    Its not you cannot use Pascal Case in both Solution and Publisher. In CRM word, we always prefer lower casing in Schema Name(it make thing easier) :).
     
    so does that mean that publisher  scheme name should be all small letter, but solution scheme name can still be capatialized, as it got auto filled with capital letter? 
     
    Yes, its by default. Even at the time of entity and attribute creation the schema name will have captial letter(we always change to lower case)
     
    Thanks, 
    Vejai SH  
     
    Please mark as answer if my suggestion helps you
  • DELDYN Profile Picture
    36 on at
    may i ask why lowercase make things easier?

    so if i use camel case like this SellOps for both publisher name and solution name, then i won't face any issues right?
  • Vejai SH Profile Picture
    560 on at
    Hi @DELDYN,
     
    When you make Schema Name = Logical Name 
    • You avoid confusion when switching between UI and code.
    • You can easily map fields in JavaScript, C#, Power Automate, etc., without cross-checking names.
    • You reduce human error when referencing fields or writing fetchXML.
    • It improves code readability and maintainability.
    When you have both logical name & schema name the same, it will be easy when you do coding, no need to cross-check especially in JavaScript.
     
     
    Thanks, 
    Vejai SH  
     
    Please mark as answer if my suggestion helps you

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Congratulations to the March Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Apps

#1
11manish Profile Picture

11manish 530

#2
WarrenBelz Profile Picture

WarrenBelz 459 Most Valuable Professional

#3
Haque Profile Picture

Haque 314

Last 30 days Overall leaderboard