SalesForce

Are you struggling to fit your migrated data into your target Salesforce environment? Is there a need for creating multiple fields? Don’t want to lose the data but don’t have the fields to migrate it to? If the answers to most or all of your questions is ‘yes’, then this article can help you achieve all the above without creating any new fields and without suffering any data loss. Where can you use this technique? Lack of fields on the Target as compared to the Source environment Data model does not match between the two environments Do not want to create new fields in the Target environment Do not have a separate custom object to hold the data Figure 1 Salesforce data model not matching How to achieve this? We will extract all the data from the source environment and insert it into the Description field of the Target environment using TALEND.  Assumptions We have migrated the data of Productsobject (OpportunityLineItem) from Source org.into a Description field (Special_Instruction__c) of Opportunity object in Target org. We are using Excel to extract data from Source environment and a Salesforce connection to push the data on the Target environment. We can also create a Salesforce connection for both the environments (Recommended way). Process Step 1: Create a Salesforce connection. For this you need 3 parameters: Username Password Security Token Figure 2 Create a Salesforce connection You need to enter all the credentials for the Source environment. Note:If you are connecting to a UAT environment be sure to change the URL in the tSalesforceConnection component. Step 2:In this step we need to extract the data from both the source files. Figure 3 Job Design in TALEND To achieve the above process first you need two files: Source File:In this file you need all the Product data (Opportunity Line Item data) along with the OpportunityId Target File:In this file you need the Opportunity Id from the Target Step 3:In this step we need to: Insert the two files into the tMap Apply an inner join between the two files. Concatenate all the product data into a single variable and add a null check to all the fields before inserting them into variables. Insert the variable into the Opportunity field. Figure 4 tMap Design in TALEND  In this method we have added “|” to separate the data you can choose another symbol as per your convenience. Note: Select the same selections in the tMap as highlighted above. Step 4: After all the description is concatenated add a tDenormalize to concatenate the records with the same Opportunity Id based on the Description field. Step 5:In this step use a tSalesforceOutput component to update the description field for the respective opportunity. Finally attaching the complete job for reference. More ways to implement the above approach: Extracting data from Salesforce rather than Excel Using other objects like Account, Contact etc. Pushing data into Salesforce with Excel Merging Product Data with Billing data Conclusion In a nutshell, we can say that whether your migration is for small or large data, you need to process your data in an efficient way. In your data migration journey, Talend can be your partner for ensuring hassle-free migration. About Girikon Girikon – a global provider of quality IT services houses a team of skilled Salesforce professionals including Salesforce consultants, administrators and developers.

Customers continue to be the most important assets for any organization and to ensure long-term relationship with your customers, it’s important to cater to their needs in the best possible way. One of the most effective ways of doing so, is to constantly upgrade your products and services, in a way that fulfils the evolving requirement of your customers. In other words, create new version of your products through new releases and upgrades. If you are leveraging the Salesforce platform, you will have to keep pace with all the upgrades that it keeps releasing time and again. What is Salesforce Upgrade? Salesforce releases new upgrade from time to time and to improve the performance, logic, and usability of your software, it is essential to upgrade it to the new version. Besides releasing regular upgrades that could be used to improve a products functionality and performance, Salesforce has illustrated seamless upgrades that are critical to customer success. Salesforce takes up to five minutes for upgrades and users will not see any difference when using the new Salesforce release. Changes with the new release will not activate by default and only salesforce admin can activate the new features using the Setup menu. What is the Impact on Interface? During the upgrade, our customizations are preserved, and Salesforce gives the same effects having the same consequences. During the upgrade, the Session Id is inactivated, and if any interface is running at that time, we’ll get ‘INVALID_SESSION_ID’ error. We cannot run our batches during the upgrade period, as the upgrade window can break our batch, we’ll have both valid and invalid data in our org. To manage this, what we need to do is: Monitor the validation/deployment results and check the post-deployment steps. If we need to run a batch after deployment checks the execution result of the batch. If it failed, we have to run it again. This has an impact on our scheduling (stop cascade batches and implement a retry every 30 minutes for example) We need to plan our batches after or before the upgrade period. We need to implement to run the same batch once again to continue the process without altering the data already processed. For a batch update to keep data consistency, we need to use transactions. It is native for batch Apex, but when using the API (custom development, ETL connector (i.e. TALEND, dataloader, etc.), we are not able to keep data integrity. The only way to keep it is by creating Apex Webservices that will be accessed by our batch. Is there any impact on Connected Users? During upgrade all the users need to invalidate their Session Idso that they are unable to connect the Salesforce until the upgrade process has finished. Users receive an error message letting them know that the service is unavailable during the upgrade and are prompted to log in again when the upgrade is complete. To manage this, we need to do: Share an upgrade timeline plan with all users so they know when you will upgrade, and how often Inform the user when they can log in into the system Share the new document, if any, if there is a change in the Salesforce UI/UX Best Practices to be followed If the Salesforce upgrade is not planned, there might be cases where end-users may not be able to access Salesforce after the completion of the update. In order to avoid unexpected service disruptions, we may need to take the following actions: 1) Enable “My Domain” NOTE: “My Domain” is required for customers who have requested the org migration. 2) Update the hard-coded references if any, for e.g. test-abc.salesforce.com and make sure to update them to the right URLs (for example, <yourdomain>.salesforce.com, abc.salesforce.com) prior to the org migration. Also, if there is any hardcoded Id in the code, make sure to update them dynamically. 3) If the Salesforce org has set up corporate network settings or any email security filters to restrict the access to only certain IP ranges, make sure to update the lists to include the newest ranges. You can whitelist the IP ranges in the Network Setting of Salesforce. 4) If there is an issue in integration following the maintenance, prepare to refresh integrations. Why to Upgrade and what are the benefits? Salesforce has the capability to work with earlier released features even if those features are supplanted by new functionality. Salesforce keeps all customers on a single version—i.e. the most recent version—of the product. Therefore, Salesforce provides the same experience, coolest Feature, advancement on compatibility and the latest bug fixes. Conclusion It is very much required to upgrade the Salesforce version to the latest release as it can eliminate the technical risks involved during the implementation. We understand that there could be a service disruption for couple of minutes but it is must have for your organisation since it could also increase your productivity. As we know that Change is the only Constant, hence we all must go with the flow and suggest the users/clients to upgrade to the newest version as soon as it is live. About Girikon:  Girikon is a Salesforce Consulting Partner, committed to deliver excellence by providing customers with wide array of quality services including Salesforce implementation, Salesforce consulting and Salesforce support.

Are you facing the following challenges while migrating data to Salesforce? Tired of deleting the duplicates manually in Excel? Excel keeps hanging up because of large data? Applying VLOOKUP again and again for the same data set? Duplicating the whole data again for UAT and Production environment? Cannot apply complex transformation to your data set? If you have answered yes to most or all of the questions above, then the solution to your problem is TALEND. What is TALEND? TALEND is an open source software integration platform which helps you to turn data into business insights effortlessly. When we hear the term “Data Migration”, questions like – What is data migration? Why is it needed? How is it done? etc., pop up in our mind. This article addresses all the basic queries on Data Migration along with the reasons for choosing TALEND as an ETL tool for Salesforce migration. Which tool should be used in Salesforce Data Migration? Selecting the right data migration tool depends largely on your needs. There are several data migration tools, but they won’t be of help if they  fail to meet the specific goals and objectives of your company.. Listed below are some points that you might need to consider while choosing an ETL tool. Let’s understand the Data Migration process before we go ahead and address the aforementioned issues. What is Data Migration and How Does TALEND Fit in? As the name itself suggests, data migration is the process in which data is transferred from one system to the other. These transfer systems can be data storage types or file formats. Data from the old system is transferred to a new system through a particular mapping pattern. The above diagram is a job in TALEND showing how simple it is to extract data from a Source, apply any tansfomation logic and push into different Target destinations. How is it done? Source Data: TALEND can be used for importing the raw data from different sources, andprocess multiple types and formats of Source data for exampleFile, Database, CRM or API. Data Cleansing: In this process we perform the following steps: Detect and Correct (or remove) corrupt or inaccurate records from the dataset. Identify incomplete, incorrect, inaccurate or irrelevant parts of the data. Replace, modify, or delete the dirty or coarse data. Data Deduplication: After Cleansing the data, Duplicate copies of data are removed from the dataset based on a pre-approved field set. Data Transformation: In this process we transform the data from the Source to match the Target Data Upload: After the transformation the data is uploaded to the Target system in which TALEND supports multiple platforms for example Excel, SQL server or Salesforce org. Why choose TALEND? Open Source Software: There are no cost implications for using “Talend Open Studio” or “TOS” since it is an open-source software. Cost is applied if there is a demand for joint data collaboration. Multiple Source/Target Format supported: We can extract the data directly from Salesforce, transform it, and push it directly into Salesforce without the need of an Excel or any Database. If in any case we do not have an Org to Org connection, we can still extract the data using Excel, manipulate, and load the data into Salesforce using TALEND since it supports all the Excel formats. Faster: We can process and transform the data much faster than Excel as TALEND provides functionalities in which we can change the format, append new data onto existing one and create or remove columns on the go. Reusable: In TALEND once the job is created the same job can be used for different target locations we do not need to transform the whole data again for different environments like (UAT or Production). In the case of any future modification we just need to append the same job and we will be spared from going through the whole process of transforming the data again. Supports Complex Data Transformation: TALEND provides the tools to perform highly complex transformations and manipulations on the data. It also provided the functionality to write custom scripts in JAVA wherever there is a need for custom transformations It can also process huge amounts of data which is difficult to manage in Excel. Conclusion: While there are several other tools for data migrations in the market, TALEND has become a preferred choice as it provides with the functionality of accessing data more easily, processing it more efficiently and moving it across various target systems very easily. About Girikon:  Girikon is a Salesforce consulting and development company offering quality IT services to clients across the globe. Based out in Phoenix, Arizona, the company has presence across Australia and India.  

Customer relationship is the key to Organizational growth and so it should be managed as efficiently as possible. Salesforce CRM can be leveraged to remain more connected to your customers while ensure better business performance. The user can do some changes in their salesforce environment according to the requirement of the customer/client to ensure that it continues to run efficiently and to improve the business. These changes can be as small as the minor updates to existing features or can be as large as new application development project. All these changes have one thing in common i.e. deployment because once the development is done and tested, it will be deployed to production. A salesforce deployment is essentially the final stage in any project, during which changes made to your instance are pushed live. NEED The changes made should be deployed to production once you are satisfied with the solution you have built (tested on UAT) but it can be challenging for the user if any of the followingis not found after deployment, Any updated or a new Component or Class which is required. Required permission is not assigned to any component or class or to any user after the deployment. HOW TO CATER THE NEED? To overcome the challenges, you must create a proper strategy and a deployment checklist. With the help ofa checklist, you can easily track the TO-DO changes that need to be done on production environment and it can be prepared during the UAT deployment. UNDER THE HOOD AND TECHNICAL INSIGHTS In order to make sure you have zero defects during deployment, there are a few best practices every business should observe and enforce to ensure the success of their Salesforce deployment. This would require usersto create two deployment checkliststo ensure smooth and hassle-free deployment Deployment checklist should be prepared in two different ways: Pre Deployment Checklist – Before Deployment Ask the user/client– Before deploying any changes to production,users/ clients should be asked about system usage so that if any error occurs, they will not be affected by it. Mostly it is done on weekends to have minimum or zero impact and the users/clients are already informed about that. Prepare excel sheet-While developing a new functionality or updating anexistingone in our sandbox which will be further moved into production,you can create an excel file where developer/admin can write the names of all the apex classes, visual forcepages, lightning components,apex triggers, validation rules, workflow rules, custom objects, fields etc. which have been created or modified for deployment. The following actions must be covered: Creation of a User Profile User Creation Creation of Roles based on the user hierarchy provided by the customer Creation of a Public group and provide access to the newly created user Roles Creation of Lead Queues and provide access to the newly created Public group Add Field value for the new Business in ‘Commercial Team’ field of Users, Campaign etc. Ring Fencing of Data; Create Sharing Rules on Accounts, Opportunities, Campaign so that no other user outside the business can view the data Creation of Price book based on the events; Share the price book with Public group Creation the Price Rules and Product Rules, if the application is CPQ. This sheet will reduce the risk of missing any above actions need to be done by the user during the deployment. Create test scripts– During the deployment process,minimum 75 % coverageis required for the test class to deploy with its apex class or apex trigger. It is highly recommended that you create a test class just after the creation of apex class or apex trigger and try to achieve coverage of 75 % or as much as possible to avoid coverage error during deployment. Backup of existing features – Take a full export of the production area where deployment has to be done. In case, something goes wrong,thenyou would have the backup to upload the data again. Disable email deliverability – Mass changes can trigger lot of system mails and notification, so disable the email deliverability during deployment to ensure your users aren’t bombarded with an avalanche of mails. Deactivate rules – Deactivate the validation rules, workflow rules, flows, process builders anything that might impact changes or prevent them from deploying correctly. Make a list of what you’ve deactivated so you can reactivate it once the deployment is completed. Make sure that you run tests afteryou’ve reactivated the previous ones andthe new ones to ensure a usergets a fully functioning environment. Prepare training and documentation – Your users may end up getting confused if you continue making changes without updating them. To avoid any type of confusion, it’s better to organize training sessions and prepare necessary documents so that the changes can be easily understood by them.                         Post Deployment Checklist – After Deployment Reactivate-Reactivate the rules or flows that you have deactivated before the deployment. CPQ Setup – If the deployment is of a whole new CPQ application then setup the CPQ configuration,create the Quote template and assign the permission to the users of this application. Assign Permissions to users – Assign permissions sets/access to the users so that they can perform the required operations which they want to perform. Visibility of Fields and Components – The fields and components which are deployed must be visible to the assigned users who should have the permission to access them. Unit Testing – After reactivating the rules and flows and assigning the permissions to the users,it’s important to perform unit testing on production to make sure all the changes arein working mode. Provide Support – If any functionality is not working or users want some changes, provide support to the users so that they can explain their concern to the support team. BENEFITS: Salesforce deployment is much more than just pushing a configuration. It isn’t complete until you’ve thoroughly evaluated it for quality assurance in production.You definitely don’t want to impact the business and the customer relationship. The‘Deployment Checklist’ creates a reliable point of reference for testing and to not encounter any challenges in your deployment. It will give you the probability of having no error on production andwill increase the efficiency of the projects deliveringand will make it more effective. CONCLUSION: Deployment can be a complex and time-intensive process. Rather than jumping into it, it’s prudent to scrupulously plan everything ahead to ensure that everything is accounted for before going LIVE. We should carefully consider the implications of the deployment and take sufficient time to build and test different scenarios before starting the actual deployment, and for that ‘Deployment Checklist’ comes up as a suitable solution. About Girikon:  As a Salesforce consulting partner, Girikon is committed to deliver excellence by providing high-end Salesforce consulting, Salesforce implementation and Salesforce support services. 

Maintaining effective customer relationships is the cornerstone of every business undertaking. In fact, it has become a key determiner of success for organizations. Today, forward-thinking organizations are leveraging robust technology solutions like Salesforce to provide superior service to their customers. As a cloud-based CRM, Salesforce helps organizations to accelerate their sales, grow customer loyalty, and augment their marketing capabilities. Most interestingly, it provides teams across an organization the ability to access the latest customer details for streamlining business processes and creating quality services and solutions. But, for this to happen, organizations require developing a Salesforce integration strategy to ensure that it partners or connects with other important systems, applications, and services. Successful third party integration is critical to turn it into a valuable business tool. The process of integration is beneficial both for users, as well as the Salesforce platform. Besides helping the platform to expand its services, integration services help in improving the operational functionality of the platform, which ultimately allows organizations to increase their customer base. It makes sense to engage with a reliable Salesforce consulting partner to know more about Salesforce integration services. What is the Need for Integration?  Today, several businesses have realized the significance of integrating their Salesforce platform with other systems and are thus trying to develop point-to-point connections with adjacent systems. However, such integrations aren’t sustainable as there are several touchpoints, which, when integrated with Salesforce, can provide value to an organization such as developing partner ecosystems, dealing with legacy systems, and more. All these will help in uncovering new opportunities to add value to your customers etc. Considering the variety of Salesforce integration needs, the integration process might become challenging and can be addressed using common integrating patterns. Common Salesforce Integration Patterns Enlisted below are some of the most commonly incorporated integration patterns that can be used to facilitate seamless third-party integrations: Migration Pattern: Data migration involves moving a data set from one system to the other. The migration pattern involved in integration allows developers to create migration services that are automated and allow the developed functionality to be shared across all the teams in an organization. Developers have the option to set configuration parameters to get access to API calls. This will provide seamless migration of Salesforce data in and out of the platform either basis as and when required via API or on command basis. Developers can also develop reusable services for facilitating periodic migrations while saving considerable time for the users. Data migration pattern can be utilized for other Salesforce integration such as data migration from legacy systems to Salesforce, Consolidating CRM systems, creating data back-up for customers, and more. The migration pattern is particularly useful while handling vast volumes of data. Broadcast Pattern: It is a one-way synchronization process that helps users to move data from the source location to multiple systems in real-time. As compared to the traditional 1:1 relationship, this pattern implies 1: many connections. Unlike the migration pattern, the broadcast pattern is more efficient as it functions on a transactional basis and facilitates faster processing of data, besides keeping it secure and up-to-date across all the platforms it has been shared across. It is recommended to ensure the reliability of this pattern as it lacks human supervision, and the majority of processes are initiated through push-notifications that are pre-scheduled. Aggregation Pattern: In contrast to the broadcast pattern, the aggregation pattern helps in migrating data from multiple sources to a single destination system. This pattern does away with the hassle of running various integrations regularly besides ensuring more reliability and data security. The template created due to aggregation patterns can be used by users to merge multiple data sets for creating reports in different file formats. Some of the most important uses of the aggregation pattern include: Creation of orchestration API that pulls data from multiple sources and processes it into a single response. Creation of a central data repository that could be used for compliance and auditing purposes. Bi-directional Sync Pattern: This pattern brings together multiple data sets across the different systems, causing them to act as a single system while allowing them to acknowledge the presence of other data sets that are being transmitted. This integration pattern comes in handy when different systems are required to accomplish other functions along with their specific tasks in the same data set. The usage of this integration pattern allows users to have a real-time view of the transmitted across the systems. Some of the use cases of this system include: Integrating multiple systems to Salesforce that leads to improved operational efficiency. Streamlined quote to cash while serving as a system of records for data that requires to be synchronized. Co-relation Pattern: While this pattern is quite similar to the bi-directional sync pattern, it differs in the fact that it singles out data sets that intersect with each other and provides bi-directional synchronization of scoped data provided that data occurs in the system naturally. This will lead to the creation of new records if they are found in all other systems apart from the concerned one. This pattern only synchronizes objects as long as they are present in both systems naturally and doesn’t discern the origin of the data object. This integration pattern is useful in cases when two systems wish to share data only if both the systems have records that represent the same contacts or objects. The Bottom Line:  Clearly, there are numerous benefits of Salesforce integration for managing data within enterprises. However, to get started using these patterns, you must get in touch with an experienced Salesforce implementation partner who can help you make the right choice. So, develop long-term and strong customer relationships by gaining a unified view of your customers through Salesforce integration.

Data loss poses a severe threat to businesses of all sizes. When sensitive data is compromised or stolen, the financial health, productivity, and reputation of a company take a hit. As data volume is increasing exponentially, opportunities for thefts and breach of proprietary information are rising significantly. While businesses are adopting strategies to prevent the loss of their confidential data, it isn’t entirely possible to avoid the same. While organizations using robust CRM systems like ‘Salesforce’ might develop a false sense of security as they store their data in the cloud, yet these systems aren’t prone to outages. While Salesforce till now provided data back-up recovery services for retrieving lost data, especially in scenarios such as ‘data import’, which might at times go wrong. However, Salesforce is about to cancel its data recovery services by the end of July 2020.  What makes Salesforce retire from their data recovery services?  Salesforce doesn’t consider their data recovery service worthy enough to be continued due to the time and cost involved in retrieving the data. Apart from this, some data cannot be recovered using Salesforce data recovery services, and an excellent example of it is the metadata. In fact, only data as old as three months can be recovered and is recommended as a last resort that, too while recovering large quantities of data. While the Salesforce recovery process requires you to pay a hefty rate of $10,000, it takes several weeks before you receive the CSV file much before you restore data to your org. What’s more bothersome is that Salesforce doesn’t assure of complete retrieval of data. With such poor services, Salesforce finally decided to call off its data recovery services without any replacement.   Alternatives to data recovery services by Salesforce  Salesforce provides three out-of-the-box options that require manual intervention: Data Loader: Using Dataloader, you will be able to export all your data manually. With a developer by your side, you will be able to automate the export process easily. Data Export Wizard: This function enables you to program a downloadable copy of your data. Once the back-up is ready, you will be notified regarding the downloading of the files via email. This allows you with 48 hours to download all the data before they expire.  Reports: The reporting function, just like Data Loader, can be used to export your data. However, running extensive reports can be taxing and time-consuming.  What is the Best Fit? In such a situation, the best approach is to use third-party applications that are available on AppExchange for data recovery and back-up. However, it would help if you looked out for features like multiple snapshots of data, comparison between production and sandboxes, and data hosting solution coupled with a mechanism for querying data. Since, the Salesforce platform is designed to facilitate integration with third-party tools; it provides for a back-up data solution.  Conclusion:   While it isn’t easy to prevent data loss, the good news is that it is easy to avoid the loss of Salesforce data with a robust disaster recovery strategy. Though Salesforce intends to back out from their data recovery services, it certainly provides for a back-up solution.  Girikon – a reputed name in the Salesforce consulting space offers wide array of IT services that can be leveraged by organizations across different sectors to fulfill their specific business needs.

Today, technology is evolving at a very high pace and Salesforce continues to be at the forefront of such a change. Over the years, this robust and innovative CRM system has been constantly introducing cutting-edge features, which has re-shaped the way businesses across the globe interact with their clients. Recently, Salesforce introduced Lightning Experience (LEX) – its newest user interface that offers a cleaner and visually appealing interface, easy navigation and many more benefits over its ‘Classic’ counterpart.  While it might be tempting to leap to the Lightning platform right away, it’s equally important to understand the benefits and limitations that the shift might bring to your organization. It’s in your interest to ask yourself the following questions before making a shift.  Are You Ready for the Change?  Users need to understand the pros and cons of adopting or making a shift to a new system. While some users might be apprehensive of making a shift as they might get accustomed to the look, feel, flow and form of Salesforce classic, those who are planning to leap should have in place a change management strategy. This will help them deal with the roadblocks that might arise during the transition and will provide them with a structured approach for supporting the shift from Classic to LEX (Lightning Experience). In fact, the sole objective of change management is to make the transition to LEX as smooth, easy and transparent as possible. Businesses can also seek the support and guidance of a Salesforce implementation partner to ensure a smooth transition.  Will LEX fulfill the needs of my Users?   It is important to ensure that the new system can fulfill the needs of every user group. This would require every user to have the necessary tools required to stay put with the new system (LEX) rather than getting back to Salesforce classic. While LEX allows customization of several features such as content density, page layout, new connectivity tools and accessibility for different user groups, there are some features that aren’t supported in LEX. It is therefore important to run ‘Lightning Readiness’ check to analyze what all are LEX ready and what all aren’t. The ‘Lightning readiness check’ should be followed by the discovery phase to understand how users are utilizing the tools available to them. The discovery phase should include a key step i.e. the technology assessment stage, which is usually conducted by a Salesforce expert who can use LEX for a couple of weeks and create an existing state of the business processes that too for multiple user groups. This will further help in developing key functionality plans, technology requirements, and wish lists, which can be used to build UX design for ensuring LEX usability. Ultimately, the design for each user group can be created. This will allow users to visually view the benefits or the change that will affect them.   How exactly will you track LEX ROI?  It is important to educate your stakeholders regarding the benefits and the potential LEX offers in generating significant ROI for organizations. According to a survey conducted in 2017, organizations leveraging LEX have enjoyed a 15 to 20 percent growth in ROI. In fact, there are several ways businesses can utilize LEX to achieve their objectives.   The Bottom Line:   In a nutshell, we can infer that though the Lightning experience offers an array of better features over its classic counterpart, it’s important to weigh in the pros and cons of the new system before making a shift. By gathering apt answers to the aforementioned questions, businesses can expect a significant rise in ROI, ensure seamless adoption and eventually enjoy increased productivity from users. If you are still on the fence, you must get in touch with an experienced Salesforce consultant who can aptly guide you throughout your Salesforce journey.