Error in deploying sandbox to production in salesforce - object

I am deploying my project from sandbox to production. And i am using "ANT" tool for deploying. But it is giving me error as given below:
Error: objects/Form__c.object(144,13):field integrity exception:
unknown (must specify either cascade delete or restrict delete for
required lookup foreign key)
Can anybody help me please.
Thanks,

Goto line no 144 of your object Form__c there will be a Lookup Field , in that field remove the 'Required' Tag , remove that tag completed and start your ant deploying again.

Sounds like an API version mismatch thing. If I recall correctly ability to reparent master-detail relationships and to mark lookups as required on DB level instead of layout level was introduced in summer'12. Your XML file is coming from sandbox without this feature so SF is complaining at the missing tags.
See release notes (pages 183-184), though they don't really mention the metadata changes...

Related

Error when assigning dashboard to new user Liferay 7.3.5

We are using liferay 7.3.5 and have about 600 users that make use of the personal dashboard. When a new user is added, they get assigned a profile and dashboard programmatically. however, recently we have ran into a problem regarding the assigning of the dashboard.
when a new user is added to the platform, the profile assigns as normal, but the dashboard will say (on the "profile and dashboard" tab of the new user) "This user does not have any private pages."
we have chosen several different templates all of which assign without fail. we have also tried to deconstruct the existing template, but only when it has been entirely cleared and is basically a fresh start, does it work again. The dashboard still works for any of the users that have gotten assigned it before it 'broke'.
this is the error code we recieved. we have not been able to trace back the FileEntry ID. we have been stuck on this matter for a while now, but it's not an option for us to rebuild a completely new dashboard.
2022-05-27 13:51:38.335 ERROR [http-nio-8080-exec-12][SitesImpl:1927] Unable to export layout set prototype 207822
com.liferay.exportimport.kernel.lar.PortletDataException: No FileEntry exists with the key {fileEntryId=884352}
Does anyone know what could be causing this error and/or how to solve it?
Your own custom servicebuilder service (with the namespace declaration GB) has been redeployed with a newer version and might be incompatible:
Build namespace GB has build number 54 which is newer than 36
You'll find more information about Upgrade Processes in Liferay's documentation, or in these two blog articles - this documentation would go beyond the scope of a simple answer on stackoverflow:
ServiceBuilder and Upgrade Processes
Building in Upgrade Support

SSIS package cannot pull from one SharePoint list, all others are okay. Where do I start?

I have SSIS packages that use the oData source to pull from SharePoint lists and libraries. Most of them work. One of them does not. The connection tests fine, but when I go to edit the data source and specify the list I want, trying to retrieve the columns gives me an error that says "An error occurred while retrieving the metadata".
There's one computed field in this list, and when I had the SharePoint Dev remove it in the development environment, the package worked. Is there any way I can configure the oData source to automatically skip this field? I may not be allowed to have it removed in production.
That computed field was already deprecated, and has been removed. It works now.

Unable to open VS2012 BI project after having to recreate Windows profile

I had to recreate my Windows user profile due to some technical problem that kept me from logging in. Now I'm trying to recover all my software, etc. I start VS2012 and opened the project I'm currently working on which is an SSDT/SSDT-BI project - database model and an SSIS project. I'm getting the following error:
Warning 1 Warning loading ADSMetricsETL.dtproj: Warning: Failed to decrypt an encrypted XML node. Verify that the project was created by the same user. Project load will attempt to continue without the encrypted information. ADSMetricsETL.dtproj 0 0
So I suspect there's a GUID or SID somewhere that identifies me as the owner of the SSIS packages and it's got my original profile's values stored identifying the "old me" as the owner. Is there any way to easily change ownership to my new profile?
For completeness sake I'll add my comments as an answer:
Change the protection level to DontSaveSensitive. This warning usually comes up when sharing packages between different users since the default protection level is EncryptSensitiveWithUserKey.
I'm glad that you do not have any sensitive information in the package -- it always best to use parameters or configurations.

How do I migrate from TFS to Visual Studio Online using the OpsHub Utility?

I am attempting to migrate to VSO from TFS and receiving the following errors:
I have administrative rights in both VSO and TFS.
Please help me figure out what the problem is.
Thank you!
Here you find answers to your all queries.
Administrative Right(s):
The OpsHub Visual Studio Online Migration Utility requires that the user that is used to create the Visual Studio Online End Point is a member of the Project Collection Administrator Group.
To grant the user that particular right, follow the following link.
http://www.opshub.com/ohrel/Resources/TFS/permissions.php?page=admin
Template Customization:
You are facing template customization error due to you have configured custom field(s) at your source end.
& such field(s) are not exist on your target VSO.
Solution for this is to delete the custom field(s) at your source end & revalidate again to processed further using migration utility. Migration on customized process templates are not supported through free utility.
You can revert customization incase you want to continue your migration with free utility with the help of following article.
http://msdn.microsoft.com/en-us/library/dd236909.aspx
You can use power tools for quick configuration of custom fields
http://visualstudiogallery.msdn.microsoft.com/f017b10c-02b4-4d6d-9845-58a06545627f
Missing Link Type(s) Warning:
You are seeing link type warning because your target VSO instance is not having Affects and Affected by link types. Still you can continue the migration with warning, in this case your Affects & Affected by link type(s) will migrated as “Related” link type.
Alternative solution is to create new project with CMMI template in your target end. This will automatically add the missing Affects & Affected By link type(s) in target VSO. After doing this revalidate again and proceed further without warning. You can remove newly created CMMI project once you are able to see Affects, Affected by link types in you project.

Sql Schema Compare will not update after CLR object installed 'Source schema drift detected'

After installing a custom CLR object Sql Server Developer Tools (SSDT) VS2012 will not allow an update. The error is "Source schema drift detected. Press Compare to refresh. After refresh same thing happens.
Tried
In settings, I set the object to just Stored Procedures.
Settings ->General -> Block on possible data loss -> tried both on and off.
This sort of loop can also be caused by a referenced SSDT project failing to build. The referenced project may be missing, unloaded, or have an error which prevents the compare from completing.
This is not an answer but a clue to deal with this problem.
I was to update a colum from varchar[200] to varchar[MAX] and got this problem as well. So I logged in the server and tried to update the database manually via SQL Management Studio which was installed there, and I got this error:
"Saving changes is not permitted. The changes you have made require the folloing tables to be drpped and re-created. You have either made changes to a table that can't be re-created or enable the option Prevent saving changes that require the table to be re-created."
Seems that re-creating table is something so dangerous that "block/unblock on possible data lose" cannot handle. So I think only if we can walk around this LOCAL warning, could we update the database REMOTELY.
But, why [200] to [max] leads to re-creating table? It does not make any sense. I tried [200] to [1000], and it did not work as well. This might be the key to this problem.
And, if you do the same update in Server explorer in VS, instead of SQL Management Studio, it works. Again, why?
This can happen when a db user "changes".
The following rather scary forum page recounts issues where foreign hackers were trying to brute-force access to the "sa" db user, with each attempt changing the sa-user's date timestamp (which is seen as a schema drift):
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/5c22a7b4-7a82-4717-a118-2475bc62705b/schema-compareupdate-error-target-schema-drift-detected?forum=ssdt
Here is also mentioned that you can query the sa-user a few times, to see if this is happening to you:
SELECT * FROM sys.server_principals WHERE principal_id=1
I am currently experiencing the same issue (that the sa-user is being modified; I know nothing about hackers yet) and am yet to find a solution.
Edit - I turned on logging in Windows Firewall via properties > logging, and we setup a blocking rule on port 3071, which had a lot of unexplained traffic. Then the problem went away.
I tried running VS as an administrator, it worked.

Resources