anytime i deploy a search (2019.1), i lose ‘public...
# sdf
m
anytime i deploy a search (2019.1), i lose ‘public/private’ settings and the whole audience config. is this a bug or some permissions gap? we are using a custom deployment role, but it’s essentially just a slightly expanded version of the ‘Developer’ role
a
I think this is a known bug 😞
m
@Albert Margarit (NS Eng Lead) don’t suppose it’s a bug that’s getting fixed in 2019.2?
a
I'm not sure, that's not owned by my team. I'll ask
d
yes, it's very frustrating. Especially when my deploy.xml has saved searches, and script deployments which depend on that search. • The search will deploy and be set to private • The script is deployed, but then fails because the search is private.
a
Understood. I'm asking the team. I'll let you guys know as soon as I get an answer. Thanks!
n
@mtsb @dbaghdanov I've run into this issue before when deploying - I believe the solution is to ensure the Publish Search permission is set to full on the SDF Developer role when deploying
message has been deleted
d
@Nicholas Klug I was using the managed "Developer" role, which apparently doesn't even have that permission. So i created a custom role, and added "Perform Search" -> "Full" (it was previously only "Edit"). But SDF still deploys the search as private
a
Hello! Looks like the "Publish Search" permission was added to the Developer role in 19.2
d
thanks
I would imagine in my test, using a different role with the Publish Search => Full, that it should have deployed the search as public though
but in my custom role, it still deployed the search as private
a
that sounds like a bug then 😞
can you reproduce with 19.2 account?
d
oddly, i don't see the managed Developer role in our release preview environment
('cause that role was inactive) ok, that seemed to work in 2019.2: • sdfcli deployed: 1) saved searches 2) scripted records
searches were deployed as public, and scripted records were able to reference them w/out errors
a
💪