Hi I encounter this issue after i deploy it another environment
DataTables warning: table id=resultsTable - Requested unknown parameter 'plan_id' for row 0, column 0. For more information about this error, please see http://datatables.net/tn/4
but on my local machine it works fine.
Related
While trying to add a new fe_users record, on save I get
(1/1) Exception
Could not determine pid
It's TYPO3 9.5.20.
We already have a lot of entries in multiple folders which could be edited without problem.
But those records were imported (by EXT:ig_ldap_sso_auth or with mysql terminal)
These records are used only to be shown (no login is used).
What configuration is missing or could be wrong?
EDIT:
as #biesior mentioned: the error message does not come from the core but from an extension. It's EXT:solrfal (in version 7.0.0)
The real error was not in EXT:solrfal. this extension just hides the error with a misleading message.
The real reason was a wrong database configuration for the table fe_users. Although it is not possible in SQL to have a default value for fields of type text (and any given value is ignored) TYPO3 expects a default value if it is configured. As this is not returned from the database it assumes an error. And EXT:solrfal hooks into the error handling and assumes a wrong error.
Hi just got the same problem.
The error message was called in solrfal ConsistencyAspect::getRecordPageId() which was called by ConsistencyAspect::getDetectorsForSiteExclusiveRecord(). I remember that I have added various tablenames to siteExclusiveRecordTables of Extension Settings of solrfal. And yes, there was one table without pid. After removing this table from list, deleting files works again.
I have ran into a strange issue in one of my SSRS reports. I get the following error:
"An error has occurred during report processing. (rsProcessingAborted)
cannot read the next data row for the dataset Defect_Summary. (rsErrorReadingNextDataRow)"
Whenever I run this dataset's query in query designer, or in management studio, the query runs fine. However, when I run the report in report builder or on the server I get the above error. After researching I have found that the issue has something to do with my parameter.
I have a parameter #PO (Production Order) where the user will provide an 8 digit number i.e. 11002575. In my query I have the following line: OrderNr / 10000 = #PO. In the database, OrderNr is of type bigint and will have a value such as 110025750020. I divide this number by 10000 so that the 8 digit #PO parameter equals the OrderNr such as 11002575.00 = 11002575. I used to use LEFT(OrderNr, 8), but found it slowed down the query so this division has worked better for me.
Anyway, here's the strange part: When I first encountered this error, and after researching, I changed my parameter to type integer (from text). This fixed the problem temporarily and the report ran fine. Then I encountered it again, so I changed the type back to text, and again, it fixed the problem temporarily and the report ran fine. I keep going back and forth with this temporary fix and have not been able to find a permanent resolution to this error, it just keeps coming back after a while of working and then all I know to do is keep going back and forth from integer to text. Can anyone help me resolve this error permanently?
Updated the Docusign for Salesforce managed package in Salesforce from version 6.2.1 (showing 6.8) up to the current 6.8.2. After doing so I'm now receiving the following when trying to access Docusign.
Final variable has already been initialized An unexpected error has
occurred. Your solution provider has been notified. (dsfs)
As an admin of the org I also get the APEX error email with the following pertinent details:
Visualforce Page: /apex/dsfs__DocuSign_Admin
caused by: System.FinalException: Final variable has already been initialized
Class.dsfs.PlatformPermissionSetService.<init>: line 32, column 1
Class.dsfs.ServiceLocator.getPermissionSetService: line 72, column 1
Class.dsfs.DocuSignConfiguration.loadConfig: line 366, column 1
Class.dsfs.DocuSignConfiguration.initConfiguration: line 338, column 1
Class.dsfs.DocuSignConfiguration.getInstance: line 214, column 1
Class.dsfs.ConfigurationService.<init>: line 32, column 1
Class.dsfs.ConfigurationService.<init>: line 20, column 1
Class.dsfs.ServiceLocator.getConfigurationService: line 60, column 1
Class.dsfs.ServiceLocator.getConfigurationService: line 50, column 1
Class.dsfs.AdminManager.findAdminDetails: line 12, column 1
Class.dsfs.AdminController.<init>: line 41, column 1
As a salesforce developer I see this as an error in the managed package code wherein they are trying to assign a value to an already initialized final type variable, likely related to a caching of Permission Set information.
I have already uninstalled the app in one of our sandboxes and reinstalled, this did not fix the error.
I installed this in a developer org that has not had the app installed before and it pulls up the VF page without issue.
Assuming this is related to my org but can't find anything in my control to manipulate. Unable to inspect the protected custom settings related to the app.
Was directed here after first level support told me they couldn't help me.
Known issue for Docusign, DFS-4536 After Install -DocuSign for Salesforce Error when accessing Package
Will update again once patched.
One of the columns I'm operating on is:
Comments VARCHAR(8000)
So basically I'm trying to insert a large text of up to even 600 characters into this column Comments. When I run my script everything goes smoothly for first 10 rows then all of a sudden I get this error:
pypyodbc.DataError: ('22018', '[22018] [Microsoft][ODBC SQL Server
Driver][SQL Server]Operand type clash: ntext is incompatible with
int')
Then again if I rerun the query, everything will start going smoothly for next 10 rows and as you might have guessed by now I get the same error again.
What can I do to fix this?
Edit:
I have tried using VARCHAR(MAX), NVARCHAR(MAX), VARCHAR(800), TEXT. I get the same error every time.
I wonder whether it is a problem with the data on row 10?
To test this, try deleting the data on, say, row 5, and see whether the error starts on row 9.
I would recommend you using pmyssql instead of pypyodbc. Seems like it is a driver level issue and switching to pymssql might help. Please follow the ACOM doc and let me know if that helps. If you still run into the same issue let me know as I can further try to help you.
I'm trying to Upsert the data to Account object using an external tool, Everything works fine but Salesforce is throwing error for few records when upserting.
I was doing the upsertion process using the external id field. Except external id field no other field is having a unique constraint.
I'm getting the following error -
SF_ERROR: DUPLICATE_VALUE
OBJ: Account - duplicate value found: unknown duplicates value on record with id: 001***********
Please help me to solve the issue.
This is happening because your trying to create Salesforce contact multiple times with same email and data
It's silly but this was happening to me because SFDC considers 'NULL' as a unique value... Mostly because Excel converted 'NULL' to text and was trying to bring in the literal word 'NULL'.