+ Start a Discussion
a.ka.k 

Einstein Analytics and Discovery Insights Specialist - Challenge 5.We did not find the correct field level security for the Predicted Tenure field.

a.ka.k
User-added image
a.ka.k
I figured it out..It is b'coz of last step related to story creation & deploy model. If they are wrong & later we rectifiey them it creates multiple  "Predicated Tenure" field in subcriber object and due to this FLS error is coming. To resolve this two ways:-
1. Delete all newly created field,story & modal.  Complete both steps (story cretaion & deploy modal) again without error. Now, give FLS to your profile only i.e admin. It will resolve the issue. If not able to delete newly created fields try second approach.
2. Login/Signup in new org. Do the steps for challenge 5 only.Install the pkg mentioned in the superbadge(subcriber object one). Create Tab. Load data. upload required CSV in dataset. Create story & deploy modal. Now, there should be only one field in Subscriber obj. Give FLS edit access for your profile. It will reslove the issue now. 
AbhishekAbhishek (Salesforce Developers) 
Hi,

Next time If you have Trailhead issues please report it here,

https://trailhead.salesforce.com/help?support=home#

https://trailhead.salesforce.com/help

So that our trailhead support engineers will look into it and get back to you.

I hope you find the above information is helpful. If it does, please mark as Best Answer to help others too.

Regards,
Salesforce Support.
manila agnihotrimanila agnihotri
@a.k - Thank you so much. I resolved the error by your approach
a.ka.k
@Chinmaya Rath 5, sometimes it difficult to delete the field created from AI. No need to create field manually.
Mohit ChhipaMohit Chhipa
@a.k, It worked for me. Thank you for your solution ! 
weno bakweno bak
It's an awesome piece of writing for all the online people; they will obtain benefit from it I am sure. If you are interested in gaming stuff then please visit my website gtacheatcode.com or you also click here for Stellaris (https://gtacheatcode.com/stellaris/).
Danielle LapidusDanielle Lapidus
When you deploy and delete multiple Discovery predictions for Challenge 5, you inadvertently create  multiple "Predicted Tenure" fields under the Subscriber object. Once you are set on your final deployment solution: Follow these steps:
#1. you must re-number the labels,names, and API names of the multiple "Predicted Tenure" fields so that your final solution is "Predicted Tenure" and "Predicted_Tenure_ _ c". (You will have to give the original Predicted Tenure field names a different number. Ex: Predicted Tenure2;Predicted_Tenure_ _ c2).
#2. Set Field level security to visible for your profile. Set View Field accessibility to Read-Only for your profile.
#3. make sure your lightning page Einstein Prediction component references the correct "Predicted Tenure" field. Click on each Predicted Tenure choice until the correct Prediction component shows on the page.)
This approach cleared the challenge for me! Good luck!
Vaibhav PurohitVaibhav Purohit
Hey Guys,

I've tried to delete the model, the story and then go through the whole process but i still get the error:
"We did not find the correct field level security for the Predicted Tenure field."

As a second approach I also used a different analytics dev edition, repeated the steps for challenge 5 but still ended up getting the same error.
Does anyone have any ideas? Any guidance is appreciated.

Thanks
Danielle LapidusDanielle Lapidus
Hi Vaibhav,
When you deploy and delete multiple Discovery predictions for Challenge 5, duplicate "Predicted Tenure" fields are created under the Subscriber object. That is why field security is not correct.
Once you are set on your final deployment solution: Follow these steps:

#1. you must re-number the labels,names, and API names of any duplicate "Predicted Tenure" fields so that your final solution has the fields "Predicted Tenure" and "Predicted_Tenure_ _ c". (You will have to give the original Predicted Tenure field names a different number. Ex: Predicted Tenure2;Predicted_Tenure_ _ c2).

#2. Set Field level security to visible for your profile. Set View Field accessibility to Read-Only for your profile.

#3. make sure your Lightning page Einstein Prediction component in the Lightning  Page Builder references the correct "Predicted Tenure" field. Click on each "Predicted Tenure" choice until the correct Prediction component shows on the page.)
This approach cleared the challenge for me! Good luck!
Renzo Rodriguez Paiva GonzalesRenzo Rodriguez Paiva Gonzales

Hi Daniel, 

I am getting this message:

"We can't confirm you mapped the correct fields on the Tenure model. Make sure you only have one model under your prediction, check the model fields, avoid using fields that may cause data leakage, and try again".

I have a model with 0.78 AUC that doesn't show any data alerts. It has the following fields: "Subscription date" (Trend cadence by year), "Churn", "Region", "Rep Name", "Payment Method", "Contract", "Online Security", and "Partner". All fields are mapped, there is only one model deployed to the Predicted Tenure field.

Do you have any ideas where the problem can be?

Danielle LapidusDanielle Lapidus
Hi Renzo, Was that the first and only model you have deployed since working this challenge? If you deleted earlier version(s), the original api label for the Predicted Tenure field was deleted as well. So you need to change the api label of the current model back to the original label. That is what the challenge algorithm is looking for. If you have only deployed one model and it is still throwing the error, if you chose the fields manually, try the autoselect method and see if that passes. Good luck!Regards,Danielle Danielle Lapidus LinkedIn ProfileDanielle Lapidus dba Danielle Olivia TefftEditor, Found in the Jewelry Box BlogOwner, Treasure Box Antiques