Skip to main content

#Error0 人がディスカッション中

Recommendation, when facing User Provisioning Error from Microsoft Entra ID to Salesforce:

I recently faced an issue with the user provisioning integration from Microsoft Entra ID to Salesforce. The error response is seen at the bottom (all included for enabling searching of this by others). 

 

Issue Origin:

The issue was caused by a duplicate user being created:

  1. Proper 'User Real' already existed, without FederationIdentifier
  2. Then the user provisioning system synchronized the users to Salesforce
  3. Since it didn't find a user with the FederationIdentifier, it created a new one 'User Dupe'
  4. We found this, deactivated 'User Dupe' and cleared FederationIdentifier, and set the correct one on 'User Real'
  5. However, the next user provisioning sync failed.
  6. The error message was unclear, but we found the user facing the issue based on a Salesforce User ID in the Entra ID provisioning error logs.
  7. We then tried to set some dummy FederationIdentifier on 'User Dupe' and tried a sync, and then we got a different error.

Probable Root Cause: 

While one might assume that Microsoft Entra ID always retrieves users from Salesforce, before an update occurs towards Salesforce, it instead seems like Entra ID is caching a table of users based on Salesforce user ids, and updates based on this invalid cache mapping (FederationIdentifier -> SF User Id). 

 

The bug overall seems to be in Microsoft Entra ID, so the issue should be raised with their support.

  

Sample Error Message Thrown in Entra ID:

EntrySynchronizationError

  • Result: Failure
  • Description: Failed to match an entry in the source and target systems User 'XX@YY.ZZ'
  • ErrorCode: UnSpecified
  • Error details: Invalid context
  • ErrorMessage: 

An error has occurred when attempting to match an entry in the source and target systems. 

 

Review the common matching failures and error details for more information. Common matching failures: 

  • The target application does not support filtering on the matching attribute. Review your attribute mappings and ensure that the target application supports filtering on that matching attribute.
  • The source entry does not have a value for at least one matching attribute. Review your attribute mappings to identify the matching attribute(s) and ensure that the entry has a value for those attribute(s).
  • The target application denied the request due to an authentication or authorization failure. Ensure that the credentials you have provided have the necessary permissions for provisioning.
  • There is an issue with the target application. It is unreachable, returned a non-specific error, or returned a non-SCIM compliant response. Contact the application developer. 

 

 

#User Provisioning #Auth Provider #Error

0/9000
0/9000
9 件の回答
  1. 2023年1月30日 14:42

    You'll need to aggregate the duration of time first:

     

    Seconds

    SUM(DATEDIFF('second',[Start time],[Complete Time]))

    Then we use Jonathan Drummey's calculation for the final result, with the aforementioned calc:

     

    dd:hh:mm:ss

    //replace [Seconds] with whatever field has the number of seconds in it

    //and use a custom number format of 00:00:00:00 (drop the first 0 to get rid of leading 0's for days)

    IIF([Seconds] % 60 == 60,0,[Seconds] % 60)// seconds

    + IIF(INT([Seconds]/60) %60 == 60, 0, INT([Seconds]/60) %60) * 100 //minutes

    + IIF(INT([Seconds]/3600) % 24 == 0, 0, INT([Seconds]/3600) % 24) * 10000 //hours

    + INT([Seconds]/86400) * 1000000 // days

    Which returns the following:

    You'll need to aggregate the duration of time first: SecondsSUM(DATEDIFF('second',[Start time],[Complete Time]))Then we use Jonathan Drummey's calculation for the final result, with the aforementioned

0/9000

I am parsing a text field for a date, pulling the date and putting it in a new field as a date. Because the text is manually updated by users, if the date is entered in an incorrect format I get an ⌗error for the new date field.

 

I tried to write a formula to flag the ⌗error, however the formula is not capturing the ⌗error. Is there a way to use a formula to flag the errors?

 

I'm currently using:

 

IF ISNULL([Field]) then 'Review'

ELSEIF STR([Field]) = '⌗Error' THEN 'Error'

ELSEIF 7 < DATEDIFF('day',[Field],TODAY()) then 'Review'

ELSEIF 7 >= DATEDIFF('day',[Field],TODAY()) then 'Good'

ELSE 'Check'

END

 

For fields with the error I'm getting "Review."

5 件の回答
  1. 2022年3月23日 14:38

    If your data is producing the value ⌗error yet your calculation is using ⌗Error, then it won't work. Tableau is literal, so the case of the word must match that in the data. ⌗error and ⌗Error are two different values in Tableau. Try changing to ⌗error in your calculation, see if that works. If it doesn't then please provide a sample of the data for us to work with.

0/9000

based on my assumptions of Tableau calc, i assume that this column in red should all be True, correct?  if not, why not. and so what exression would make this True?

2 件の回答
  1. 2018年8月2日 13:58

    Hi Jon,

     

    Try trim(segmentlabel1)="Now 2 CPD" may be due to trailing spaces it may causing the issue

     

    Try and let me know or lets is it possible to attach workbook with fake data so that it will be easy to help

     

    Kindly mark this answer as correct/helpful to close the thread

     

    BR,

    NB

0/9000

Hi,

I'm getting ⌗Error and Null values instead of dates under column 'Initial target date'.

Format for both 'Initial target date' and 'actual closure date' is same in source file(tableau prep). 'actual closure date' is showing up correctly.

 

#Error and Null values instead of dates?Thanks in advance!

A

4 件の回答
  1. 2023年7月4日 10:25

    Hi @Atul B​ ,

     

    This is happening because "Initial Target closure date" field is not in proper format and it contains both text and date information.

    Hi @Atul B​ , This is happening becauseOne alternative to create a date field from this field is as follows. This replaces the TBD fields with NULL value. For other calculations you can handle the NULLs accordingly based on the data requirement

     

    IF [Initial Target closure date]='TBD'

    THEN NULL

    ELSE DATE([Initial Target closure date])

    END

     

    Regards,

    Ajay

    Please upvote and mark as Best Answer, if it helps you :)

0/9000

Hello,

Can someone assist me on this request?

How do I only show the Max(Date) and its corresponding dimension value in the report when all other dimensions are all in the report view.

 

For example, from this table, I only need to show the category for a user who has the last date.

  1. XYZ - Car -11/03/2022
  2. ABC - Car -04/01/2022

Get the Corresponding Dimension value for the Max(Date)Thanks in advance.

10 件の回答
  1. 2022年9月21日 21:55

    Yes you can:

    {FIXED User, Category:Max(If Quantity >=1 THEN Date end)}=Date

0/9000

Created bins. But getting only null and #error value as output.Created bins in tableau. All I am getting is null and #error value as output. Please let me know how can I resolve this. Sharing image for the same.

4 件の回答
  1. 2022年6月3日 21:59

    I found wrapping the function that is used to calculate the values I am trying to bin in the INT() function resolved this issue for me. Example = INT(datediff('day', birthdate, someDate)/365.25)

0/9000

I have custom Oracle SQL returning a number of columns including a Timestamp "Due date".

 

The source data has some typos where the date has been entered incorrectly so as to be a syntactically correct data but wrong by a few centuries Tableau seems to struggle.

In some circumstances e.g. Year(), Month() etc Tableau seems to work with these dates but in others  e.g. ATTR() it does not, yielding an "⌗Error"

 

Can anyone explain?

Date Typos and #Error

6 件の回答
0/9000

This is the first time I've encountered this problem. I've got 2 dimensions, both strings, yet when I try to concatenate them into a calculation it gives me a value of ⌗Error and I can't figure out why. I'm using a TDE, and developing this 10.2.

 

Calculated Field Producing #Error

6 件の回答
  1. 2017年7月14日 15:23

    What happens if you wrap both fields in STR()?

0/9000