• Shane Oliver
  • NEWBIE
  • 0 Points
  • Member since 2019

  • Chatter
    Feed
  • 0
    Best Answers
  • 0
    Likes Received
  • 0
    Likes Given
  • 0
    Questions
  • 5
    Replies
Hello,

If a user doesnt not have accessibility to certain record types, will he still those records ?

Thank you for sugestion
  • April 10, 2019
  • Like
  • 0
I have a requirement to build a custom component for Customer Community to create a new case. On the form I have a lookup field to a custom object that doesn't want to work. Are lookups to custom objects suppose to work in communities? Here's a simplified version of my code.
 
<aura:component implements="force:appHostable,flexipage:availableForAllPageTypes,flexipage:availableForRecordHome,force:hasRecordId,forceCommunity:availableForAllPageTypes,force:lightningQuickAction" access="global" >
<aura:attribute name="Case" type="Case"  />
<aura:attribute name="newCase" type="Object"  />
<aura:attribute name="simpleNewCase" type="Object" />
<aura:attribute name="newCaseError" type="String" />
<force:recordData aura:id="caseRecordCreator"
                  fields="Location__c,LocationTest__c,Number_of_Required_Extensions__c,Primary_Use_for_Numbers__c,Extension_End_Range__c"
                  targetRecord="{!v.newCase}"
                  targetFields="{!v.simpleNewCase}"
                  targetError="{!v.newCaseError}" />

<!-- First we initialize the form -->
<aura:handler name="init" value="{!this}" action="{!c.doInit}" />

<lightning:recordEditForm objectApiName="Case"
                          onsubmit="{!c.handleSaveCase}" >
                        <lightning:inputField fieldName="Location__c" />
                        <lightning:inputField fieldName="OwnerId" />
                        <lightning:inputField fieldName="LocationTest__c" />
                        <lightning:inputField fieldName="ContactId" />
                        <lightning:input label="Input" value="{!v.case.LocationTest__c}"/>
</lightning:recordEditForm> 

</aura:component>


({
doInit : function(component, event, helper) {
    //Standard way to load a record template using Lightning Data Service
    component.find("caseRecordCreator").getNewRecord(
        "Case",
        "0122a0000008c9lAAA",
        false,
        $A.getCallback(function(){
            var rec = component.get("v.newCase");
            var error = component.get("v.newCaseError");
            if(error || (rec === null)){
                console.log("Error initializing record template: " + error);
            }else{
                console.log("Record template initialized" + rec.sobjectType);
            }
        })
    );
},

    handleSaveCase : function(component, event, helper){
    //This is how we link the new Contact with the actual Account Id
    //component.set("v.simpleNewCase.AccountId", component.get("v.simpleUser.AccountId"));        
    //alert("{!v.simpleUser.AccountId}");
    //component.set("v.simpleNewCase.ContactId", component.get("v.simpleUser.ContactId"));

    //Standard way to save a record using Lightning Data Service
    component.find("caseRecordCreator").saveRecord(function(saveResult){
        if(saveResult.state === "SUCCESS" || saveResult.state === "DRAFT"){
            //resultToast is a pop-up window that show messages.
            var resultsToast = $A.get("e.force:showToast");
            resultsToast.setParams({
                "title" : "Case saved",
                "message" : "The new case was created",
                "type" : "success"
            });

            $A.get("e.force:closeQuickAction").fire();
            resultsToast.fire();
            $A.get("e.force:refreshView").fire();
        }else if(saveResult.state === "INCOMPLETE"){
            console.log("User is offline, device doesn't support drafts.");
        }else if(saveResult.state === "ERROR"){
            console.log("Problem saving case, error" + JSON.stringify(saveResult.error));
        }else{
            console.log("Unknown problem, state: " + saveResult.state + ', error: ' + JSON.stringify(saveResult.error));
        }
    });
}})

Why isn't the Location lookup showing any values?
I have built a custom object that I want to use to hold roll up summary data on the Opportunity Amounts that are related to it. As you cannot use Opportunity records in a Master Detail realtionship with a Custom object, I have created a Junction object with a lookup relationship to the Opportunity, and a Master Detail relationship to the Custom Object where the roll ups will happen.

Having set up all the objects and relationships, the junctions and roll ups work, but the issue I am having is with automation. I have set up Processes that create a new junction record and copy over the relevant fields from the Opportunity (at either creation, or update to closed won), but am struggling to automate the completion of the Master Detail field on the junction object that will hold the roll ups.

I have tried copying a text formula that matches the name of existing Custom Object, but keep receiving ID errors that prevent the process running. How else could I populate the Master Detail field on the junction object when it is created?

Any suggestions that could help me make this work would be gratefully accepted.

PS: I know that another option is to use Flows, or a declarative rollup solution/roll up manager, but I am trying to see if I make this approach work.
  • July 20, 2018
  • Like
  • 1
I want to integrate worldpay payment process through salesforce visualforce pages.
is their any way to do this payment integration?

In March i contacted support regarding this issue in March (3/13/2017)

https://success.salesforce.com/issues_view?id=a1p3A000000eyKVQAY 

And received this response
"I have confirmed with my Internal Team. the KI article provided by you is the same regarding the issue which you are facing as of now.
Our RnD team is working on that and planned to be resolved in Next Major release."

Does anyone know any workarounds or has seen this issue? It is with CK Editor. 

Thank you,

Lisa