24

To fetch objects from a managed package using the unmanaged package.xml, you need to explicitly call for each object, as the wildcard only retrieves objects outside a package. To retrieve layouts you need to include the full (namespaced) object name before the hyphen, and the full (namespaced) layout name after the hyphen. So for a packaged layout over a ...


17

There is a catch in case of cases and work orders objects when it comes to quick actions. In the article under Actions on record pages there is note that says Actions on cases and work orders appear in a different way than on other records. On case and work order records, the page-level action menu contains custom buttons and supported standard ...


13

Yes it is possible. See the Update - Success at the bottom: Old Answer - close but not so much Resizing the VF Page within a Page Layout is not possible though there is an option on the Page Layout that allows scrollbars for the embedded content. Another option is to (1) make the "embedded" Visualforce Page a Visualforce Component, and (2) write a VF Page ...


12

Here's what I did.... I was receiving this error when trying to do a whole bunch of changes to my internal customized code base (uninstalled an unmanaged package which was basically a way of migrating stuff from another instance, but I was tired of it being coupled to this unmanaged package). Here's how I dealt with them, one by one: Save error: ...


12

This occurs when the field definition itself is marked as required, you should see a little blue dot next to the field when viewing the layout. As apposed to being marked as required on the layout, which shows a red asterix next to the field (which you can edit via the toolbox icon to the right of the field). Custom Fields you can control the 'Required' ...


12

Buttons don't have a corresponding "button-level" security. There are at least three ways to get around this: Write a Visualforce page that overrides your default layout. Have that Visualforce page determine if the button should be rendered. Use page layouts and assign different layouts by profile. Unfortunately, you can't use permission sets this way. ...


11

Sfdcfox answer looks fine to me, however I have some remarks to point 1. and it is quite an improvement so I decided to not leave it as a comment but as a seperate answer, because some people may find it more useful. The problem with overriding default layout is that it's very hard to maintain-everytime you want to add the new field to object you have to ...


10

It is easy, just follow this steps: 1) First create a new Visualforce page. Go to Setup - Develop - Pages and click on the New button. For standrard controller select Event. Save the page: 2) Now go to the standard event page layout and edit it: 3) Over there in the Visualforce Pages area find your page. But insert a new section first. Then just drag and ...


10

Yes Page Layouts can be included in Change Sets. If you are not seeing your changes in the target environment there are a few things you can check. If there are new fields, you have to include the fields in the Change Set to push the fields onto the object. Page Layouts are only the UI of how a record looks. You have to push the object / field changes also. ...


9

Jesse, thats quick create in action. Just for completeness for other users: Roger Mitchell answered on Twitter as well: https://twitter.com/RogerMitchell/status/412985773496221696 it's called Quick Create. Can toggle from User Interface in Setup. Layout is not editable. Make your own http://blog.jeffdouglas.com/2011/08/12/roll-your-own-salesforce-lookup-...


9

It seems you are right, you can't add the button to the layout. This seems to be a special behavior on user, since on other objects it works as you may have noticed. But you can use a custom link instead, which practically does the same, but only looks a bit different and is placed at the custom-links section on the layout. If you are OK with the look, then ...


8

The answer to this question is in the question. Without record types, you have no way to change the page layout on the fly. Any editable field that is on the layout will be presented to the user, and there's no way to specify that a user doesn't have "create" access to a field but does have "update" access to the same field. Any other solution would involve ...


8

If you don't use these fields at all, you can set them to not Visibile in the field accessibility, even for system administrator. You won't see them in page layout and that should fix your problem.


8

I think you can infer it, if a field is Createable and not Nillable and not DefaultedOnCreate. SObjectType.Account.Fields.Name.Createable && !SObjectType.Account.Fields.Name.Nillable && !SObjectType.Account.Fields.Name.DefaultedOnCreate The DescribeFieldResult does not surface this directly (thanks Farid Kognoz) If you don't mind to use ...


8

If you don't want to download Visualstrap, you can add a namespace to your bootstrap. A guy at Dreamforce did a tutorial on it: http://bracketlabs.com/blog/2014/1/20/bracket-labs-dreamforce-roundup-visualforce-and-bootstrap Basically, you download the bootstrap source. Find bootstrap.less Surround whole document with .bs { } Recompile Add to SalesForce


8

Finally I have fixed it...Thanks to bob_buzzard ... The case feed is enabled via the Setup -> Customize -> Cases -> Support Settings -> Enable Case Feed Actions and Feed Items. Once this is checked, users have the case feed view or regular record view based on the "Use Case Feed" setting in their profile or assigned permission set. I have just disabled ...


8

In order to do this you would use RecordTypes Create the record types for each of the differing account groups Create page layouts to go with each record type Create a WFR to set the record type based on your criteria Assign the Page Layout to the appropriate profile and record type This works well as long as you do not have a bazillion different record ...


7

A VisualForce page can only be added to an object's Page Layout if it declares the standardController attribute and its type must match. <apex:page standardController="MyObject__c> <c:fileUpload.... </apex:page> I don't think there's any workaround for this The other alternative is to declare a new Home Page Component -- it would ...


7

This package has been out on AppExchange for a number of years: https://appexchange.salesforce.com/listingDetail?listingId=a0N30000009wZkUEAU I've not used it, but reviews are positive, and I've always kept it in the back of my mind for a rainy day.


7

You named the Related List Label "Supplier Relations Escalation", so that is what it is called on the Page Layout. You can see it on the far right of your options.


7

OK, pleased to announce I solved my own question. There were two issues. I had a misplaced ')' in my code. Don't need that extra paren. It's quite true that autocomplete is not valid field for VisualForce. But there's a handy prefix 'html-' that allows many fields to be passed through to the page. That worked to get the autocomplete attribute through. So ...


7

yes it is. go to Case --> buttons, link, Actions then find the Label "edit" and select the action edit. .. then you can override the std page with that vf one. Now, say if you want to choose between a std page and the vf page? What you'd do is create a routing VF page. So, when the user clicks edit, he goes to the router. based on what ever criteria (i.e....


7

Unfortunately formula fields cannot be viewed on the edit page layout. The only workaround I see is to override an Edit mode with a custom visualforce page. There is an Idea to turn this feature on: Read only field available on edit layout


7

No, unfortunately it's not possible without using workarounds described here: End of javascript sidebar workarounds? Note that these kind of workarounds are not supported by Salesforce and are likely to break in future versions. The Standard Edit is very restrictive and less customizable than the View is - that's one reason some of us still use the ...


7

You basically have three options: Change the RecordType of the record in question. Change the Profile of the running User Implement a Visualforce override Likely, only door number 3 is viable here. If you want to go that far, you could parse the existing layouts using the Metadata API and then use the page parameter to query for the correct one. You could ...


7

Please refer to this: https://help.salesforce.com/articleView?id=actions_in_lex.htm&type=0 In Lightning Experience, actions display in the Global Actions menu in the header, on related lists, on list view items, and in several places on a record page. Where they appear on a record page depends on the action’s type. [...] The page-level ...


7

To use an icon, specify a SVG file named component.svg in the bundle, where component is the name of the component (e.g. if the component name is helloWorld, the file is helloWorld.svg). You can't use standard icons by name, though you could copy the necessary code from SLDS if you'd like. To specify a label, use masterLabel in the component.js-meta.xml file....


6

I think there are three general approaches you can take here: (Preferred) Use the $Profile global variable, in conjunction with detecting the Record Type either from URL Parameters or from the object' RecordType.Name field, in a giant case statement. For instance, the following page could be used to override the Account object's New action, assuming that ...


6

You can create Fieldset on that object and then iterate that field set on your VF page. You can iterate field set like this on VF page - <apex:repeat value="{!ACTFields}" var="f" > <apex:inputField value="{!testDetails[f.fieldPath]}" required="{!OR(f.required,f.dbrequired)}" /> ...


6

This is impossible. Triggers operate on the database level and can be initiated from many different places (the page layout, api, your custom code, etc.) so there is nothing in the trigger to indicate what initiated the DML operation. What you can do is figure out the business logic that drives which layouts appear to which users (this is based on a ...


Only top voted, non community-wiki answers of a minimum length are eligible