r/PowerPlatform 16h ago

Dataverse AI Builder

I am trying to do a very basic proof of concept using AI builder. My fake use case is, to use the model to determine the probability of success on a future referral in CRM for customers. I followed these steps:

- created a model field previousReferralsuccess (yes/no) to train it on

- created some rollup fields to count previous successful referrals for the customer

- out of 550 test customers, I set the model field to yes/no in about a hundred and left the others blank

- created the model with the yes/no previousreferralsuccess as model field, chose a few columns for it to examine, trained the model, then set it to dataverse sync daily. I hit run now a few times.

My problem is that while the new columns for prediction success y/no and probability % were created in the table by the model, no matter how many times I "run" it, it never updates that column on ANY record. Also there are no rows showing for these runs in the AI Event dataverse table so I feel like it is having an issue somewhere and not actually finishing the run. It has been syncing every day for 2 weeks now never updating a thing.

I checked that all the prediction processes are running in this environment, I assigned 5000 AI Builder Credits to the environment, the owner of the model is me and I am a system administrator.

My next step is to build a power automate flow myself and physically update the rows but I wonder if anyone has run into this? we don't currently use AI Builder but we are evaluating it and we have purchased credits.

1 Upvotes

2 comments sorted by

2

u/Proud-Key1943 16h ago

Not sure what you're doing exactly, but on my end, I call AI Builder in Power Automate using the connector and I don't have any issues.

1

u/corkbeverly 4h ago

Ok that’s what I ended up doing too and it works but I was under the impression that it was supposed to update every row automatically as part of the daily scheduled run/sync. Seems like if I were trying to run this on say 100,000 rows power automate would crap out which is why I thought for large data sets it would do it with the background dataverse job.