jbatalha

Thank you for your answer. The thing about id_values is that they are being displayed to the user... so if it is displayed, it has to make sense to them. A great deal of our companies' internal organization relies on Client numbers, so it's not an option to change them all over. I will try your code to change the id_values just after I create the clients and see if any info is lost when using those. Best regards.

Hello, Thank you for the reply. I'm not very excited about opening remote mysql connections between these two servers. It defeats the point of using the API for anything else. But... if there really isn't a clean way to do it, I'd love to hear feedback on exactly what do I need to change in the database in order to make it work consistently.

I've dug around trying to find a way to assign the Client's id_value field through the API, but I can't seem to find it. Can anyone point me in the right direction?

Ah now I get it. I was missing that extra encapsulation array. Thanks for the timely response. Rock on.

Hi guys, Thank you for the quick responses. @Tyson: I am using the API SDK and integrating it with Drupal 7. This is a snippet of my code: $api = new BlestaApi($url, $user, $key); $params = array( ... ); $response = $api->post("clients", "create", $params); //dsm($response->response()); dsm($response->errors()); This is the output of $response->errors() in Krumo Debug: (Object) stdClass error (Object) stdClass message (String, 28 characters ) An unexpected error occured. response (String, 25 characters ) Parameter is not optional As you can see, neither the error nor the response hints at what field is missing. In big models with dozens of fields this is a huge hurdle.

Hello, We're experimenting with Blesta. We are trying to migrate our client list to the Blesta installation. We've managed to connect and find the right model to call, but we keep getting the Error that required fields are not being included in the array being sent over to Blesta. Problem is, the API just says that a required field is missing, not WHICH required field is missing. This complicates matters greatly and makes developing integrations very very slow. Is there a workaround, patch or something that we can use to have Blesta tell us which fields triggered the required error? And if there isn't, could you point me to the location in the code where I could maybe make it happen? Thank you in advance, João Batalha