Table Editor Troubleshooting Guide

This topic explains how to diagnose and fix the following common problems that can occur when working with the Table Editor visual.

Note: To review all cases, log in to https://help.insightsoftware.com/ and access the Power ON Knowledge Base articles. For further assistance, you can also submit a ticket through this support portal.

Column Type Configuration Setting is Not Showing up in [Column Properties]

Symptom: The property Column type is not showing up at all.

Cause: There can be three reasons for this: one or more of the following properties are not set correctly:

• Source Table – case sensitive, must match the table name
• Web service
• Connection Name / Type

Solution: Please read the relevant chapters in this document.

Cell Cannot be Selected, No Value can be Entered

Symptom: You have a write-back capable cell, but you cannot click into the input field, you cannot enter any value. The cell is not showing the selected status – default format is red bordered.

Cause: Most possible cause is that the column was renamed in the Power BI report. Each column that you use as a write-back target should have the exact name as it is in your SSAS model, or in case of SQL only connection, the name of the columns should correspond to the SQL table columns. It’s very typical, that for instance in SQL you have a CustomerName column, which is renamed to Customer Name in the report.

Another reason can be that the Source Table property is not set properly. Please read the relevant chapter in this document.

Also make sure that Don’t summarize is set for the field in question.

Solution: Match the names. You can give your desired header title for the column in the [Column Properties] » Title section. Examine the Source Table property, set the field to don’t summarize.

Please refer to this articles: Troubleshooting Writeback and Dropdown columns

Missing ID

Symptom: You receive a Missing ID message when you try to save modifications.

Cause: The followings can be:

1. Your target SQL table for the write-back does not have a primary key defined
2. The primary key of the table is not imported/visible in your model
3. The primary key field is not part of the column collection of the visual
4. The Column Type property is not set to ID for the field.
5. The column has been renamed.

Solution: Depending on the cause you should make the following adjustments:

1. Create a primary key on the table (see pre-requisites) and import it to your model
2. Import your existing primary key and make it visible in your model
3. Add the primary key field to the visual. You can turn the visibility of for the column.
4. Set the Column Type property for the primary key to be ID.
5. Match the column names as it described in the pre-requisites section.

Network Error

Symptom: You receive Network Error message when you try to save data.

Cause: You may get this error typically in the following cases:

• the write-back service URL is not set correctly – or it is malformed - in the [Data Entry] settings
• the write-back service is not reachable or offline
• bad connection name or/and type was specified
• the license service is stopped unexpectedly
• Missing files in the web service folder, or typo / malformed strings in the web.config file
• Windows / Kerberos authentication issue
• Missing Service Principal Names
• Missing Active Directory permissions for service accounts
• Report server URL web service URL format mismatch
• Invalid SSL certificate

Solution: Make sure that the write-back service is up and running and reachable (firewall not interfering) as it is described earlier in this document. Verify that the referenced connection exists in the write-back service configuration and the connection type is selected correctly.

A particular error can indicate a license service failure. Please refer to this article: Error: The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state

If you encounter CORS issue, please check the web.config file of the write-back service for typo-s, and also missing DLL-s and config files inside the web service folder. As a last resort, try updating the web service file following these articles:

• How to update the service manually - Azure Cloud
• How to update the service manually - On Premises

If you encounter SSL error, make sure that the certificate is issued by a trusted authority for the full qualified domain name of the IIS server, or that the certificate is set to ignore by the client’s browser in case of self-signed certificate, or if the certificate is issued internally by your organization and you try to reach the report outside of the organization domain.

If you are using Power BI Reporting Services on-premise, make sure that the Report Server URL and the web service URL format matches. Either both have to reference the machine name or the full qualified domain name, and both have to be http or https.

In case of on-premise installation in a domain with Windows Authentication, make sure that Service Principal Names are created for your SQL and SSAS servers and the correct domain users are used for the services. An SPN is also needed for the service account that is running the PPWebService on the IIS machine as the Application Pool user. Make sure that delegation is enabled in your Active Directory from the App Pool’s user (which has to be a trusted user) to the SQL/SSAS services. If these are not set correctly, Kerberos authentication issues can occur, which might result in HTTP 403 or 404 errors or appearing log-in popups. Please refer to the following article and contact your internal IT team: Troubleshooting IIS Windows Authentication with Kerberos

The Visual is Not Working in Power BI Desktop or the Settings are Not Shown

Symptom: The visual is not rendered, or Table Editor specific setting are not displayed (like [Data Entry], [Column Properties], etc.)

Cause: Generally, there can be two reasons for this:

• your machine is running out of memory, therefore Power BI Desktop cannot render the elements properly

• your Power BI Desktop Cache is outdated.

Solution: Free up memory on your computer by closing other applications. For clearing the Power BI Desktop cache, please refer to the article in our Knowledge Base at: Clear Power BI Desktop cache

Save Failed

Symptom: You receive Save Failed message when you try to write-back to the selected table.

Cause: You may get this error if there is a configuration error in your visual, the write-back service is not configured properly, or in the following cases:

• there is a custom validation implemented that prohibits write-back
• SQL objects are interfering with the data modification TSQL statements (like security policies, triggers, unique constraints, etc.)
• the service account used by the write-back service does not have permission on the underlying SQL database to make the necessary modification on the source table

Solution:

• Check if the service account has the necessary permissions, the password has not expired
• Verify that RLS policies or triggers are not prohibiting the operations

As there can be various reasons for this error, review the paragraphs in this chapter and please also visit our Knowledge Base to find the solution at https://help.insightsoftware.com/

If you were not able to overcome your issue, please submit a ticket on our support site we will contact you shortly to help you investigate and fix the problem.