I want to move standard button override (Clone) on custom object through Outbound change Sets, but I'm unable to find this position in possible changes.
In which category Button Overrides are stored?
Custom buttons and links are listed in change sets under 'Button or Link'. To deploy the Page Layouts to which they are assigned, be sure to add it to the change set under 'Page Layouts'.
If you want to deploy a button overridden with a Visualforce page, you will need to deploy the whole object, the Visualforce page, its Apex Classes, and any components that are in the Visualforce page. In addition, once you have deployed the pages and classes, you will need to go into the new environment and give the appropriate profiles access to them, otherwise navigating to the page will give them an 'Insufficient Privileges' error.
If you want more finely-grained control over what specific metadata components you are deploying (and you don't simply want to do it manually in the target org) then you should consider using the ANT-based metadata migration tool that Salesforce provides. It has some more power and flexibility in terms of migrating sub-components of metadata. Here is a link with a little getting started video for that, and here is the documentation.
Related
I am new to Microsoft Dynamics. I managed to create new solution and know how to add web resource to particular page like Contacts. Also, I have added few buttons to Ribbon control with their actions.
Now my problem is, I want to add a button either to ribbon control or anywhere in page, which I can access in complete CRM (like I can do in Master Page of asp.net), and which will help me open my web resource.
For example, if I click on Charts bar, web resource should be visible, otherwise it should be hidden.
My question may be lame, because I am very new to CRM Dynamics, kindly suggest my way is correct or I need to take some different approach?
If I understand it correctly you're looking for a way to add a button to multiple screens without need to modify each of them separately. (To avoid the pain when modifying all the ribbons or all the forms.)
In that case I'd suggest creating a separate JS web resource with code that adds a button with desired functionality, styling etc. And use Form Libraries Manager from XrmToolbox to bulk add the resource to all the forms.
Let's say a user has a list of projects, and each project has it's own set of various collection items of charts, reports, tags, etc associated by project._id
When a user selects a project, all the associated collection items are viewable by route, for example /project/<projectId>/chart/<chartId>
Currently, a user can only view one project at a time. If he opens up a new tab or a new browser, he can still only view the one project. If he switches the project, all the other tabs/windows reactively change to the new project. This is because currently the project is tied to Meteor.user.profile.projectId (but I am looking for a better way).
I would like to change this behaviour so that tabs and windows are independent of each other. If a user pastes project\project1 into a new window it should load that and it's associated collections even if his current tab is in project\project2. I hope that makes sense.
I'm not sure how to accomplish this. I am looking for suggestions and solutions. Thanks.
I believe that this can easily be accomplished using session variables:
set a default somewhere in your client code, Session.setDefault('project', 1) (or make sure that project being undefined is handled gracefully)
when a user selects a project, set the variable:
Session.set('project', [selectedProjectId])
Wherever you need to decide which project to show: Session.get('project')
I am working on a website using DNN as my Content Management System of choice, and I'm running into an issue where the main content area and the side area will switch based on which page you are on.
In the .ascx file I know I can write a conditional based on the URL you're on:
<% If Request.RawUrl.Contains("piece-of-url") Then %>
but I was wondering if there is a more permanent or reliable way to mark a page, just in case the page name changes, or if there are pages underneath that page that may not have the same styling (although, I can include the extension as a way to get around this).
Thanks for your help.
In DNN if you want to change the way the page functions, base on the page you are on, you would typically either define a separate SKIN as Brent Mannering suggests, or apply a differnt module to different pages on the site.
That being said, you can also target the "TabId" of DNN pages, in the code for the ASCX file for the Skin you could define functionality based on the tabid.
When I've needed to do this, I've created a 'Bookmark' module and added it on the page.The bookmark module just stores a value pair in the settings, in my instance I was using values like <"HotelHomePage", "Hilton"> or <"DestinationHomePage", "Sydney">. This way, page name doesn't matter, you can change the page name, move the page to a different parent, but as long as the bookmark value on the page stays the same, you will always have it.
Just make sure that a bookmark exists for each page you need it on.
I'm using Views in Drupal to show node teasers. I would like now to show the complete node on the left side of my page, nearby the Views, and update it when the user click on a different teaser (better using AJAX).
what's the best method to implement it. I was considering to use a lightbox, but it a bit complex (a lot of complications... such as parsing the content with javascript again.. etc).
See screenshot: http://dl.dropbox.com/u/72686/viewsAndNode.png
Thanks
A quick and dirty approach would be to use an iframe to hold the node content. Users would then be able to switch between nodes without reloading the page, which is I assume your goal. I don't think there is away to achieve what you are trying to do with views out of the box. Have you looked into using panels?
Here's what might be a clean way to do it, of course in drupal there's always many ways to accomplish things.
Providing the content for the ajax call
Install the services module
Setup a service that provides your node as you want it to be displayed
Create the placeholder for your content
Install the Panels Module
Create a empty fixed width panel to contain the node you want to load
Load the view into an adjacent panel
In your controlling view
Add a PHP view header and use (drupal_add_js('script.js')) to add a custom js file to the page. or add this to a custom module, or even your theme.
Re-Write your view node links to help put the js events together
Setup your javascript events
Use add_js to add a custom javascript js file to the page
In the custom js add an event to the view links that will poll the services module and load the node into the placeholder panel
I've solved using the lightbox, and just removing the html code I don't need from the node template with php if the parameter "lightbox=true" is passed with the link.
I'm working on a site that can be displayed to the user in several different ways, kind of like themes, but more functionality related. So basically, the page you are viewing is in a certain state (based on the user, country etc).
The rendering of the controls on a page will vary a bit depending on the current state, and I want this to be easily configurable. (For state A, hide this field in this control, for state B show this icon etc).
In a standard web site, a control would just access a section in web.config to get the its current configuration, but now I want the control to get different configurations depending on the state the page is in.
Any suggestions on how to implement this?
Why not just save the relevant UserControl Properties values in a database for each state. This way states can be added or modified on the fly later.
I choose to create an interface for getting configuration settings that directly mapped to ConfigurationManager.GetSection(string sectionPath).
I then injected (using Spring.Net) a class that used the built in configuration manager, but tried to resolve the section path at different levels depending on the current state.
So it started by trying to get the configuration from "[CurrentState]/Application/MyControlConfiguration", if not found tried the default "Application/MyControlConfiguration". Worked pretty well...
The controls didn't have to be aware that the application can override configuration settings depending on state.