nebkam / netsuite-restlet-php-sdk Goto Github PK

Based on https://github.com/RSM-NetSuite/INFSCRM/issues/97

I have an deployed restlet that accepts basic json as a post. Which example would work best for this? Thanks ahead of time!!!

Is this possible on your end @silvesterk @Vodzo ?
@Shinhan your branch won't be affected

Currently, scripts are parametrized by their IDs in config.json
What we were afraid of, deploy URL param can (and does) differ in sandbox VS development
So, how do we handle this?

1. Parametrize the full URL?
2. Parametrize the path?
3. Parametrize script ID and deploy ID as a touple?
4. Something else?

In any case, it will have to be a BC breaking change, since we're changing int to string or array or something else..
Please comment your thoughts @silvesterk @Shinhan @Vodzo @tabonka

U OldCrmPaymentItem bi bilo lepo namestiti da transactionDate i lastModifiedDate budu DateTime objekti. Verovatno je isti problem i sa PaymentItem koji ima vrlo sličnu strukturu.

Primer podataka koje dobijamo od servera:
{ "recordType": "customerpayment", "lastmodifieddate": "15.06.2021 12:16", "trandate": "22.02.2021", "customer": "16377", "line": "1", "tranid": "46737", "amount": "5000.00", "invoice_old_crm_id": "514809", "appliedtotransaction": "Invoice #01-2105867" }

Monolog ili nešto drugo, na način tako da svaki korisnik ove biblioteke može na svoj način da loguje u fajlove, Mongo, MySQL ili nešto drugo.

Trenutno bilo ko moze da procita podatke o tome koje departmane imamo, ko su nam zaposleni i slično smatram da je to potrebno anonimizovati.

File: src/ApiClient.php

private function bootstrapGuzzle(?LoggerInterface $logger): Client
		{
		$stack = new HandlerStack();
                // The line with the method
		$stack->setHandler(Utils::chooseHandler());
		if ($logger)
			{
			$stack->push(Middleware::log($logger, new MessageFormatter(MessageFormatter::DEBUG), LogLevel::DEBUG));
			}

		return new Client([
			'handler' => $stack
		]);
		}

Error message: Call to undefined method GuzzleHttp\Utils::chooseHandler()
Guzzle version: ^6.3

Changing the Guzzle version is not a possibility .

I quickfixed the issue on my local by changing the line in question with the following code:

$stack->setHandler(new CurlHandler());

Allegedly, fail is because of the field custitem_item_old_erp_id in the suiteQL query, which field doesn't exist in the production environment.
I've assigned @silvesterk because he implemented the method

Napomena: ovo treba i u v1.

Originally posted by @Shinhan in #27 (comment)