I have Lightning Web Components called list.
And when I try to do SFDX: Retrieve Source from Org,
To get my classes from Apex class.
I get the following error:
20:32:09.428 Starting SFDX: Retrieve Source from Org
=== Retrieve Warnings
FULL NAME TYPE MESSAGE
───────── ──────────────────────── ──────────────────────────────────────────────────────────────────────
list LightningComponentBundle Entity of type 'LightningComponentBundle' named 'list' cannot be found
20:32:10.344 ended SFDX: Retrieve Source from Org
I need help,
Thanks!
I created a new project with the command:
SFDX: Create Project with Manifest
Then, I right-clicked on the package.xml file in the manifest folder,
and selected:
SFDX: Retrieve Source in Manefist from Org
This worked.
(not a real answer but too long for a comment)
What's the exact command you're running to fetch it. If the command you run doesn't explicitly mention username/alias - check what happens when you open the default org (sfdx force:org:open) - by using default org you might be connecting to wrong org and the component really isn't there.
Maybe "list" is a reserved keyword?
Can you definitely see the component in the org. Setup -> Lightning Components contains it? When you open the developer console, query (tick the "Tooling API" checkbox at the bottom!) and run
SELECT Id, FilePath, Format, Source
FROM LightningComponentResource
ORDER BY FilePath
Is the component in there somewhere? https://developer.salesforce.com/docs/atlas.en-us.api_tooling.meta/api_tooling/tooling_api_objects_lightningcomponentresource.htm
Do you have other tools available like Ant + Migration tool or even Workbench. You should be able to run a full metadata retrieve with package.xml similar to
<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
<types>
<members>*</members>
<name>LightningComponentBundle</name>
</types>
<version>52.0</version>
</Package>
In your question there might be possible these issues:
1- When you authorize your org with VS code then might be possible your org is different and when you retrieve that is different.
2- When you deploy your code after that can be possible you delete that file, then this error can be shown.
I hope you find the above solution helpful. If it does, please mark it as the Best Answer to help others too.
Thanks and Regards,
Suraj Tripathi
Related
I am an owner of an App Registration in AzureAD. The SAVE button is greyed out when I try to save the manifest. I am able to get an error if I upload the manifest. The error is generic, "Failed to save manifest." I am looking for a troubleshooting path. I will not turn down solutions either.
I've added myself as an Application Administrator, but it didn't work.
It depends on what you modified.
Please double-check the content comparison before and after the modification to locate the properties that may be problematic.
When you try to upload a previously downloaded manifest, you may see the above error. This is likely because the manifest editor now supports a newer version of the schema, which doesn't match with the one you're trying to upload. We recommend try the following.
1.Edit the attributes individually in the manifest editor instead of uploading a previously downloaded manifest. Use the manifest reference table to understand the syntax and semantics of old and new attributes so that you can successfully edit the attributes you're interested in.
2.If your workflow requires you to save the manifests in your source repository for use later, we suggest rebasing the saved manifests in your repository with the one you see in the App registrations experience.
Here is a similar SO thread you could refer to.
I'm still new to Liferay and using Liferay 6.2
what i'm doing:
I am trying to add a document manually into my database using insert statement.
I inserted into dlfileentry, dlfileversion and AssertEntry.
Also, i created a folder with the valid name and file.
The issue:
upon entering the Documents and Media portlet, i can see the document name there but when i click on checkout, it will prompt a error saying that Documents and Media is temporarily unavailable. however i am still able to download the valid document.
Am i doing something wrong? Personally, i feel that i am missing one more table for the database but i'm not sure .
Thanks!
Yes, you're doing something wrong: You should never write to Liferay's database with SQL, as there might be more data required than what's directly visible to you. Obviously, you're running into exactly such an issue.
Liferay has an API which you can use locally, from within the same application server, or remotely as JSON or SOAP service. You should exclusively use this for write access to the database.
Alternatively, you might consider WebDAV access to your document repository as the way to add more documents to the document library.
I can't make Sitecore Analytics working. I have Sitecore 6.6.0 (rev. 121015) and installed Sitecore DMS.
1) when i go to Sitecore->Marketing Center i get error XML Parsing Error: no element found
2) when i go to Sitecore->Content Editor, choose element and press Analyze->Reports I get error You do not have permission to see any item reports
3) In Content Editor when press Analyze->Goals get Cannot use Analytics with a database that has no definition items error
4) in logs I see following:
"Exception: System.InvalidOperationException
Message: Cannot use Analytics with a database that has no settings"
5) If I change url that i get trying to open Marketing Center (changing Marketing%20Center.aspx to Marketing%20Center/default.aspx) I get Cannot use Analytics with a database that has no definition items error
6) I have in my Sitecore.Analytics.config this tag:
<setting name="Analytics.DefaultDefinitionDatabase" value="web" />
I tried to give access to analytics database from SQL Management Studio, but didn't help.
What could be the reason of this error, and how to solve it?
Your errors seem to suggest that the database is missing data. Did you use the database provided on this page, http://sdn.sitecore.net/Products/Sitecore%20V5/Sitecore%20CMS%206/Update/6_6_0_rev_121015.aspx ?
Go to the link above, scroll down to Download DMS 6.6.0 rev. 121015 for Sitecore CMS 6.6.0 rev.121015 and click the Download DMS 6.6.0 rev.121015 under SQL Server. Attach this database to your server and try again.
I haven't seen these errors, but it sounds to me like Sitecore is not able to access the Analytics database at all. You do have a connection string in ConnectionStrings.config named "analytics"? Try using the sa account just to make sure it's not a permissions issue. Don't forget to change it back from sa either way.
(caveat: I haven't used DMS yet, just OMS... it's possible I am way behind the times)
Publish your site (to web). You might be trying to analyze data that isn't live.
I just erased my previous answer as that was a consequence of what was wrong, but not the actual cause...
In the Analytics code, the Marketing Center node is requested from the current database. If it cannot find that item (which IS in the master database), you get the error.
But the code will NOT find the marketing center item if the security settings prevent the anonymous user read access...
That is where the error occured for me, when I was an anonymous user... And effectively, when looking at the security settings for the Marketing Center Item I found that inheritance had been blocked, hence preventing read access for the anonymous user...
Another reason this error sometimes occurs is when you have a production environment where there is no access to the master database.
Since the Analytics code uses the "master" database as the default definition database unless otherwise specified in the config settings, you could add the following to analytics.config:
<setting name="Analytics.DefaultDefinitionDatabase" value="web" />
That way, it will fallback to the web database in case of a production environment without master database.
Hope this helps...
Erwin
The issue is due to Sitecore not being able to read the definition items in the master/web database (depending on the Analytics.DefaultDefinitionDatabase setting).
The items it is looking for are:
/sitecore/system/Marketing Control Panel
/sitecore/system/Settings/Analytics
When the request is running, the user is default\Anonymous. Using Access Viewer, make sure there are no security settings disabling read access to these items. This includes parent items that would have a trickle-down effect.
I am executing the query for my custom object created in SFDC. but i am getting the following error:
{'[{"message":"\nSELECT FS_Account_Name__c from FS_Work_Order__c\ERROR at Row:1:Column:34\nsObject type 'FS_Work_Order__c' is not supported. If you are attempting to use a custom object, be sure to append the '__c' after the entity name. Please reference your WSDL or the describe call for the appropriate names.","errorCode":"INVALID_TYPE"}]'} Thoough have written the correct table name as given while i created the Custom object. PLease help.
First thing to try: does it work properly when run as the system administrator profile? If so then it's certainly a permissions issue. Things to checl
The object is deployed (Setup > Create > Objects > Edit > Deployment Status)
The profile has permission to query the object.
If not, does that same query work from inside the developer console? If so I can't think of what it might be, except connecting to production instead of a sandbox or vice versa.
How do I delete an Apex class and trigger in Salesforce Enterprise Edition using Eclipse?
In order to delete a trigger from a production org using eclipse you will need to use the following steps(assuming you have a sandbox org):
Through the web interface in your sandbox org, inactivate the trigger
Refresh your sandbox project in eclipse and deploy the inactive trigger to production
Refresh your production project in eclipse, right click on the trigger and select delete
Accept the option to delete from server
I believe the above steps will work, however I have only ever removed components from a production org using destructive changes & the Ant Migration Toolkit.
To use the Ant Migration Toolkit for a destructive change you would need to setup the destructivechange.xml file to look similar to this:
<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
<types>
<members>MyTrigger</members>
<name>ApexTrigger</name>
</types>
<version>21.0</version>
</Package>
There are full instructions on how to propogate destructive changes on developerforce.
I had a near-duplicate question and landed here. I want to delete a class with just the Force.com IDE (Eclipse) from my production org. Inediger described how to deploy the destructive change set using the Ant Migration Toolkit and guessed at how to do it in the Force.com IDE. In my attempts with Force.com IDE version 20.0, Inediger's steps 3 and 4 will prevent you from deleting the class/trigger in your production org.
Here's the natural attempt to delete a class in the Force.com IDE:
Click the class. Press delete.
"Are you sure you want to delete file 'myClass.cls'?" ... OK
"The requested operation will only delete the resource locally. Would you also like the resource to be deleted from the server?" ... Yes
At this point the file is deleted from your project and your dev org, but it remains in your production org (and the admin web interface won't let you delete it there) so you continue with:
Deploy to Server.
Enter production org credentials.
Next. Next.
Look for your class in the Deployment Candidates list--but it's not there!
Unfortunately, your class won't be listed with the Deployment Candidates because the Force.com IDE has already lost track of that file (because you deleted it--if you're in this boat recreate the class in your dev org and follow my instructions below).
We need to delete in production before we delete the file locally (I think we're walking the Force.com IDE through constructing one of those destructive change sets and deploying it for us):
Edit the class's matching *-meta.xml file (from the Force.com IDE).
Set the status to Deleted: <status>Deleted</status>. Save.
Right click your class, Force.com | Deploy to Server.
Enter your production org's credentials.
You should see your class as the only deployment candidate!
Check the box for "Apply Action?" to Overwrite your class.
Next your way through the rest of the wizard.
If you're following along in the Salesforce admin web pages you'll notice that the class disappears from your dev org after saving in step 2. It disappears from your production org when you get the green check mark after step 7.
Finally, I delete the class from the Force.com IDE as I normally would. When it asks me if I want to delete the file from the server I say no because we've already taken care of it. I also Add/Remove metadata components and uncheck the class name to get rid of the warning message.
The easiest way to do this is to delete the file from your project in Eclipse (not removing from the server because that doesn't work) and then you right click on the FOLDER (i.e. Triggers / Classes) and choose Deploy To Server.
When the dialog which shows want you want to deploy appears, the class/trigger in question will be highlighted as a red row, meaning you can check it for deletion from the production org.
The easiest way to do this from Eclipse is to edit the -meta.xml file for the class you want to delete. All you need to do is change the 'Status' field from 'Active' to 'Deleted'.
When you save the -meta.xml file the the corresponding class will immediately be deleted from your production org. The class & .xml files will still be in your local Eclipse folder - but then you just can delete them locally.
One of the ways I have tried was to:
1) Go into the meta XML file for the trigger [in Force.com IDE] and set the status value to "Delete".
2) Then after saving that .xml file, I deploy the trigger to production.
I kow for a fact that should delete the file. I have done it with a class file as well but unfortunately this was a test class file and I forgot to delete the other associated files that the test file provided test coverage for and so I lost significant overall cumulative Test coverage due to this mistake. Fortunately I saved the file before i deleted it and was able to re-deploy the modified test class back to production and all was OK again.