Power Platform Community Forum Thread Details

I'm hitting a widespread issue in the New Column panel (Tables → [table] → Columns → + New column) in make.powerapps.com where every secondary/advanced configuration field is missing or non-functional, regardless of data type. This isn't limited to one field type — it's consistent across everything I've tested:

Single line of text: Format → Text does not display a Maximum length field

Autonumber: Not selectable as a Data type option when creating a new column. Workaround (create as Text, save, reopen, select Data type again) sometimes surfaces it, sometimes doesn't — inconsistent even using the documented workaround

Lookup: Related table picker only shows the table I'm currently creating the column on — no other tables appear as options

Whole Number: No Minimum/Maximum value fields shown

Date and Time: No Behavior options (User Local / Time-Zone Independent / Date Only) or Format selector shown

What I've ruled out:

Reproducible across 2 different browsers (tested with all extensions disabled)

Reproducible across 2 different networks (home network and mobile hotspot, with antivirus/web-protection fully disabled)

Reproducible across 2 separate environments (Default and a freshly created Sandbox)

Not a licensing conflict — tested removing "PowerApps and Logic Flows" license from my user, issue persisted (currently have Dynamics 365 Customer Service Enterprise vTrial, Dynamics 365 Sales Premium Viral Trial, Power Automate Free, Copilot Studio Viral Trial, Power Apps Plan 2 Trial, Microsoft Fabric Free, and Power Pages vTrial assigned)

Not a classic-UI issue — confirmed I'm accessing via make.powerapps.com → Tables, not Advanced Settings/classic customization

Additional context:

I also see a Content Security Policy violation in the browser console referencing localcdn.centro-dev.com:5555/floodgate.bundle.js.map — unclear if related or a separate unrelated issue, but flagging it in case it's relevant

Separately, the Business Rule designer also fails validation with "you haven't added an action" even after correctly configuring and applying both a Condition and an Action (using both drag-and-drop and the toolbar "+ Add" method), reproducible after Publish and in a fresh Sandbox — possibly related to the same underlying rendering issue, possibly separate

Tenant type: Individual/personal tenant (KJZLLC.onmicrosoft.com), Default and Sandbox environments both affected, Production environment type.

Has anyone seen this pattern before, or know what's different about this tenant configuration that would cause an entire class of "secondary field" UI components to fail to render across the maker portal? Happy to provide screenshots, console logs, or environment details as needed.

Categories:

Microsoft Dataverse with Power Apps

Hi,

This sounds less like a specific column-type issue and more like a broader maker portal/UI rendering problem affecting Dataverse metadata controls.
A few things stand out:

The missing properties span multiple unrelated column types (Text, Number, DateTime, Lookup, Autonumber), which suggests the secondary configuration components are not loading rather than individual feature limitations.
The Lookup behavior is particularly telling. If the related table selector only shows the current table, the metadata required to populate the relationship picker may not be loading correctly.
The Business Rule designer validation issue occurring alongside the column editor issues further points to a client-side rendering or metadata-loading problem rather than a table configuration problem.

Regarding the localcdn.centro-dev.com:5555/floodgate.bundle.js.map CSP violation, source map failures themselves are usually harmless, but the fact that you're seeing portal rendering issues across multiple experiences makes me wonder whether a required script bundle or dependency isn't loading successfully in the tenant.
Since you've already ruled out:

Browser-specific issues
Network filtering/security software
Environment-specific corruption
Licensing changes

I'd investigate the following:

Open Developer Tools and check the Network tab (not just Console) for failed .js, .json, or API requests when opening the New Column dialog.
Compare behavior using an InPrivate/Incognito session with a brand-new user account if available. This will help determine whether it's tied to the maker profile or tenant-wide.
Verify whether the issue occurs in a newly created Developer Environment (if you can create one) versus the existing Default/Sandbox environments.
Capture a HAR trace and screenshots because this is beginning to look like a platform-side issue rather than misconfiguration.

The key clue for me is that both the column designer and Business Rule designer are failing in ways that suggest metadata-driven UI components are not initializing correctly. I haven't seen this as a normal tenant configuration setting, especially when basic controls render but all advanced configuration sections are missing.

At this point I'd strongly consider opening a Microsoft Support ticket with a HAR file and console/network traces. If support can reproduce the behavior in the tenant, they can check whether a backend feature flag, incomplete rollout, or portal regression is affecting the maker experience.

Curious whether anyone else with a personal/developer-style tenant can reproduce the same symptoms, particularly the missing Lookup table selector and Date/Time behavior options. Those two issues together are a strong indicator that the metadata configuration panel itself isn't loading completely.

Thanks & Regards,

Manoj Annavajjala